Collect appointment requests
Give callers a clear way to share what they need. Prepare a calendar action for review when your integration is ready.
- Reception intake
- Service questions
- Reviewed calendar drafts
PRIVATE PILOT
Answer routine questions.
Review the next step.
Build a customer support or reception agent around your business information. Test the conversation, inspect its sources, and review any message or calendar action before it leaves your workspace.
Start with sample data. Live channels require separate setup and testing.
Appointment intakeIllustrative flow. No live call.
Consultation requestDraft prepared for review
Not sentOne workspace for the work around a conversation
Business knowledgeWorkflow testsAction reviewsRun history
Start with a useful jobA smaller first pilot.
A smaller first pilot.
A clearer result to check.
Choose one repeatable request. Define what a good response looks like and where your team takes over.
Prepare a useful sales follow-up
Capture the question, use case, and preferred next step. Review the recipient and message before anything is sent.
- Enquiry qualification
- Demo request intake
- Consent-based follow-up
Answer from your business information
Add your FAQs and policies. Inspect the retrieved source passages and decide when a request needs a person.
- Policy and FAQ answers
- Source references
- Human review paths
Explore the processFrom a customer question
From a customer question
to a reviewed next step.
Open each step to see an example. This walkthrough runs entirely in the page. It does not contact a model, access a calendar, or send a message.
01Define the agent’s jobRole and boundaries
Reception assistant
Answer published service questions, collect appointment preferences, and flag requests that need a person.
Boundary
Do not confirm availability or a booking without a verified calendar result.
In the workspace: configure the role, instructions, language, and workflow in Agent studio.
02Test a customer requestExpected path and evidence
“Can I book a consultation?”
A useful test checks the greeting, the next question, and the point where the agent should ask for help.
- Call-workflow simulations check defined conversation paths.
- Knowledge search previews the source passages a model could receive.
- Live model tests are separate and remain blocked until an operator enables them.
A passing simulation does not prove live model quality or call reliability.
03Review the proposed actionExact content before execution
Calendar draft
Review the event, time zone, and consent record. Approval applies to that saved draft; execution is a separate step.
Nothing has been booked in this example.
Real execution requires an enabled integration and a confirmed provider result.
If the provider outcome is uncertain, check its receipt before deciding what to do next.
A process your team can inspectKnow what the agent used
Know what the agent used
and what happened next.
Keep the question, the workflow, and the review in view. Start with the parts you can test locally.
Keep answers connected to a source
Store text and Markdown knowledge. Preview retrieval before testing a model response.
Test the path before using a live channel
Build a call-workflow simulation or publish a versioned automation. Inspect each saved run.
Review the exact action
Inspect message and calendar drafts, record consent evidence, and approve a specific payload.
Find what needs attention
Read saved transcripts, leave feedback, and review uncertain requests without silently retrying them.
Clear expectations
What this private pilot includes
This is an early product for evaluation. It is not a generally available, managed calling service.
Build and inspect
Configure agents, edit call-workflow simulations, search uploaded knowledge, run local automations, review drafts, and record contact preferences.
Prepare a controlled live test
Provider-backed text, browser voice, selected calling routes, and external actions need credentials, access gates, consent checks, and live acceptance tests.
Verify your operating setup
Check authentication, legal notices, regional rules, recovery, monitoring, and real provider behavior. Native apps also need builds, signing, and device testing.
Bring one use case and a way to measure it.
Document the questions, approved source material, escalation path, and result your team will review.
Before you start
Practical questions
What can I try without connecting a provider?
The private workspace includes agent setup, call-workflow simulations, knowledge retrieval, local automation steps, action drafts, and a contact consent ledger. These local paths do not make calls or send messages.
Can the agent make calls or send messages today?
Live routes are implemented as controlled pilots. They need operator configuration, credentials, consent checks, and end-to-end verification with the chosen provider. This preview does not promise live service availability, delivery, or production reliability.
Can I use an Indian or international phone number?
You can store a number and its carrier details in the workspace. Actual calling requires verified ownership, a supported carrier setup, regional permissions, and live testing. The product does not purchase or port numbers for you.
Can I choose my model and infrastructure?
The text runtime and selected voice pilots use provider adapters. A private text-inference endpoint is configurable. Every provider, model, and deployment still needs its own setup and acceptance tests; support is not universal.
Are the mobile apps available in app stores?
The web workspace adapts to mobile screens. Android and iOS packaging source is included, but device acceptance, native builds, signing, and store release are separate steps. No store release is claimed.
Start with a request
your team already understands.
Use a small test set. Inspect the results. Decide what needs to change.