Agent inbox3 active
DM
Delivery updateEmail · 10:14
1
SK
Supplier callbackVoice · live
AL
Address confirmedSMS · 09:42
9:41● ● ●
SKSupplier lineConnected · 01:42
Agent

Can we move order 1842 to the afternoon window?

Supplier

Confirmed for 14:30. I’ll send the update by email.

Context packetCase #1842Email ✓SMS ✓Voice ✓Human review ready →
Conversation operations / 08

An agent without a channel cannot finish the job.
Give it a real inbox and number.

Let an operational agent continue through the channels people already use—email, SMS, and voice—while preserving the conversation context required for follow-up and human handoff.

For support, operations, and workflow teams that need agents to participate in existing communication channels.
Conversation flow builder

Map the case across
email, SMS, and voice.

Start with a real communication workflow. We will identify the channel transitions, context the agent needs, and the point where a human should take over.

What you get
  1. 01Channel sequence
  2. 02Context and handoff points
  3. 03Suggested Pilot app methods
Start with one real workflowAbout 2 minutes

Do not include credentials, secrets, or customer data. By submitting, you agree that Pilot may use this information to respond. Privacy Policy.

Conversation continuity

One case.
Every channel attached.

Many operational processes eventually require an email response, a text update, or a phone conversation. Connecting each channel through an unrelated automation stack fragments context and credentials. Pilot packages communication endpoints as agent-callable apps so they can participate alongside search, company data, and internal systems.

@
Email

Provisioned inbox and sending

Primitive provides account, inbox, send, receive, search, reply, and conversation-level methods.

Phone

Voice and number management

AgentPhone exposes phone-number and calling capabilities through a typed local application interface.

Message

SMS and conversations

The same communication surface supports messaging and conversation history for follow-up workflows.

Handoff timeline

The context travels with the conversation.

  1. 01

    Provision an endpoint

    Create or connect the email or phone identity the workflow will use.

  2. 02

    Define the communication task

    Give the agent a narrow action such as monitor, draft, reply, notify, or call.

  3. 03

    Combine context from other apps

    Search, customer data, or company intelligence can inform the interaction.

  4. 04

    Keep the channel history

    Conversation methods preserve the thread needed for later steps and human review.

Technical basis

Specific product surfaces.
Inspectable in the docs.

Product reviewPilot release 1.13.9Inspect documentation
  • 01Email account and inbox lifecycle
  • 02Send, receive, reply, and search
  • 03Phone numbers, voice calls, and SMS
  • 04Typed conversation methods