Skip to content
DEMO MODE

Nothing leaves this browser. No phone number, no provider, no messages sent.

Carpe

Settings

Workspace, seats, answering hours, exports, and appearance. There is no login in this MVP: a seat is an identity you switch into.

Workspace
Name

Loading

Sending number

Loading

Provider

Demo, nothing leaves the browser

Line status

Loading

Seats

Anyone can pick up any thread. The message carries whoever was in the seat when it was sent, so the creator sees one continuous conversation from Carpe and the team can see who answered.

    Working hours and the SLA clock

    Edits here are held on this screen and every number below recomputes from them straight away. Writing them onto the workspace record is a store action this build does not carry, so a reload comes back to the saved week.

    Loading the answering week.

    Export

    Loading the export queue.

    Appearance
    Accessibility

    Message bubble contrast

    Apple's own send blue measures 3.6 to 1 against white bubble text in dark mode and 4.0 to 1 in light. That is what makes the thread read as a real iPhone conversation, so it is the default, and it is below the WCAG AA floor of 4.5 to 1 for body text. High contrast swaps in a deeper blue at 5.6 to 1 in both themes. Bubble shape, tails, receipts, and tapbacks do not change.

    Did the coupon move to 20?
    Asking before I film.
    Still 15 through Friday.

    Read

    Consent and opt out

    TCPA applies from the first message. Consent is stored as a record with a capture time and a source, not a checkbox, because the question that gets asked later is when and how they agreed.

    • STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, and QUIT block the thread immediately and send the required confirmation.
    • START, UNSTOP, and YES re-enable it.
    • Message history is kept after an opt out. We own the record, the provider does not.
    • The FCC April 2025 rule requires honouring a revocation by any reasonable means, including free text. A keyword list alone is not compliance, which is why the suppression list lives in our own database.