Skip to main content

Keep customer email with the record.

Start the 14-day trialor walk a real job in the demo
To send, you need email permission right now and a sender set up.

On the Operator plan, $399 a month. Put the whole crew on it. Nobody pays per person.

The FL Permit Pay Inbox showing a customer conversation beside the texts, email and county-mail channels.
FL Permit PayA live Inbox. One customer conversation beside the texts, email and county-mail channels it can move between.

Prepare, send, and record without collapsing the states.

Four things stay apart: who the customer is, the documents you picked, what the provider tried, and any outcome we are not sure about.

  1. Step 1

    Open the customer or job

    Start from the record that owns the conversation so customer and job context stay connected.

  2. Step 2

    Write it like an email

    A real subject line and a body you can format: bold, italic, links, bulleted and numbered lists, a heading and small print. Expand the card to full screen when it is a long one, and read the customer's copy before you send it.

  3. Step 3

    Sign off once, not every time

    Save your name, company and license number in settings. Then the messages you write yourself go out under it. Mail the product writes, like a proposal or a pay application, is not signed for you. That wording is ours, not yours.

  4. Step 4

    Add eligible documents

    The job documents you pick go out as private FL Permit Pay links. Each link runs out after a while.

  5. Step 5

    Review the recorded outcome

    Check the record after the send. The status you see is the one we wrote down. That includes Failed and Unknown.

  6. Step 6

    Read the reply as a conversation

    Replies arrive as a thread, not a stack of forwarded text. The quoted history folds behind Show earlier so you read the new sentence first, and photos the customer emailed back appear as thumbnails you can open.

Each outcome is recorded for exactly what it is.

Five states. None of them rounds up.

  1. 01
    Queued / SendingFL Permit Pay is attempting the provider request. No outcome has been recorded yet.
    In flight
  2. 02
    SentThe provider you set up took the request. That is not proof it arrived, landed in the inbox, was opened, or was read.
    Provider accepted
  3. 03
    SkippedWe never asked the provider. Either it did not qualify, or the setup was not done.
    Skipped
  4. 04
    FailedThe provider rejected the request.
    Failed
  5. 05
    UnknownAn ambiguous result. It is left for review and never automatically retried.
    Review

Everything lands on the record.

LiveMessage threadEvery attempt and what came of it lands on the customer or job thread. There is no separate outbox to dig through.
LivePrivate document linksAttached files go out as links that expire, so a job document never floats around an inbox after the link is dead.
ConditionalInbound repliesReplies come back to the job when reply email is set up for your company; replies that fail trust checks appear quarantined, never silently dropped.
ConditionalPhotos the customer sends backFiles attached to a reply are listed on the thread. Images show as thumbnails, everything else as a download. They are kept for 90 days; after that the thread still names each file and says the file is no longer held, rather than showing a dead link.
LiveThe thread keeps itself currentAn open thread checks for new messages about every 30 seconds, and again the moment you come back to the tab or the signal returns. If you have scrolled up to read something, it leaves you where you are.

Keep every word with the customer next to the job.

One path, with permission checked, carries the message, the documents that qualify, and what the provider said back.

What you can send and see depends on your email setup and your role.
Start the 14-day trial