Skip to main content

Client email

Keep customer email with the record.

Prepare a customer message from the record, add eligible job documents as private links, and keep the provider-call outcome with the thread.

Get startedSee how it works
Sending requires current email permission and a configured sender. A sent status records provider acceptance, not inbox delivery or reading.

Customer email

Facilities desk follow-up

Not sent
Recipient
f•••@mailer.test
Job
Harbor reroof
Sender
Configured
01
SubjectPermit document follow-up
02
Private linkPermit packet · time limited
Attached
03
Provider outcomeNo request attempted
Draft
Example dataAn example draft. It shows record context and provider state, not delivery, opening, or reading.

How the work moves

Prepare, send, and record without collapsing the states.

The customer context, selected documents, provider attempt, and uncertain outcomes remain distinct.

  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

    Prepare the message

    Write the subject and message before any provider request is attempted.

  3. Step 3

    Add eligible documents

    Selected customer-job documents are shared as private, time-limited FL Permit Pay links.

  4. Step 4

    Review the recorded outcome

    FL Permit Pay records queued, sending, sent, skipped, failed, or unknown without presenting provider acceptance as delivery.

Send outcomes

Each outcome is recorded for exactly what it is.

The provider-call outcome stays with the thread. Sent records acceptance, not delivery.

  1. 01
    Queued / SendingFL Permit Pay is attempting the provider request. No outcome has been recorded yet.
    In flight
  2. 02
    SentThe configured provider accepted the request. Not proof of inbox delivery, placement, opening, or reading.
    Provider accepted
  3. 03
    SkippedEligibility or setup meant no provider request was attempted.
    Skipped
  4. 04
    FailedThe provider rejected the request.
    Failed
  5. 05
    UnknownAn ambiguous result. It is left for review and never automatically retried.
    Review

Where the message lives

Sent is not delivered.

LiveMessage threadThe customer or job record owns the conversation, so context stays connected.
LivePrivate document linksEligible customer-job documents are shared as private, time-limited FL Permit Pay links.
ConditionalInbound repliesRouted replies are recorded when reply-domain intake is configured; replies that fail trust checks appear quarantined.
Out of scopeDelivery proofA sent status records provider acceptance, not inbox delivery, placement, opening, or reading.

Next step

Keep customer communication beside the work.

Use one permissioned path for the message, eligible documents, and the recorded provider outcome.

Sender setup, inbound reply intake, and visible records vary by environment and current role capabilities.
Get started