01
Task templates
Begin with common support work such as account lookups, request creation, lead capture, or a custom form.
Removesstarting every support automation from an empty schema.
Actions
Let your Agent finish the simple work you allow.
Add read-only lookups, support requests, forms, buttons, or your own API behind explicit permissions and review rules.
Confirm email · Test in the sandbox with 100 evaluation credits · No card for setup
Allowed taskBlocked task
Turn on only the tasks you choose.
Everything else stays off.
Your help center. Your inbox. Your team.
See how it worksAsk what an Action can do.
This page runs on Communicate. Type a question below and the assistant on this page answers it.
How it works
Define the task before the Agent can run it.
Actions stay predictable because inputs, permissions, and the customer-facing result are configured together.
Action
DraftTask
Create support request
Input
Conversation and email
Result
Ticket reference
Permissions
RestrictedAccount lookup
Read only
Create request
Allowed
Billing change
Blocked
Run result
CompletedCustomer
Context included
Support request
Created
Conversation
Updated
WHY IT MATTERS
Approved tasks finish in the Conversation. Everything else stays with your team.
What changes
Resolve the request where the customer already asked it.
A useful Agent does more than acknowledge a task. It either completes the allowed work or brings in the right person.
- 01
Simple work ends in a real result
Lookups and approved support tasks return their outcome in the Conversation instead of creating another queue.
- 02
Permission stays visible
Allowed, blocked, and review-required work remain explicit for the team configuring the Agent.
- 03
Your systems remain the source of truth
A custom API Action can use structured inputs and return a controlled response without giving the Agent open access.
Designed for the edge cases
Narrow Actions are safer and easier to trust.
Each Action should do one understandable job with a result your team can verify.
02
Allow and block rules
Keep read-only tasks separate from mutations and reserve sensitive changes for a teammate.
Removesgranting broad access just to automate one small task.
03
Structured API calls
Define the endpoint, required inputs, and returned fields instead of passing free-form customer text downstream.
Removesletting unvalidated conversation text reach an internal system.
04
Observable outcomes
Keep the request, state, and result attached to the Conversation your team already reviews.
Removeschasing an automation log in a separate tool.
Task templates
Allow and block rules
Structured API calls
Observable outcomes
Used in production
Already answering customer questions.
- Teams building software
- Teams making content
- Teams running everyday tools
- Autoposting
- Vrid
- Niyam
- FAAD Network
- Nimblocity
Pure Digital- QCall
- Serri
- The Medical Insurance Exchange
Proof
The allowed task is visible before it runs.
Communicate keeps the permission boundary close to the customer request.
01 · Input
Required information is explicit
The Action defines the fields it needs instead of guessing from incomplete context.
02 · Access
The permission is narrow
Read, create, and blocked work stay separate.
03 · Result
The outcome returns to the thread
The customer and teammate see what happened without changing tools.
Compare
Approved Actions without an open-ended automation layer.
Compare the control your support team keeps around each task.
Task result
CommunicateInside Conversation
Macro or linkCustomer leaves flow
Custom automationCustom UI
Permission model
CommunicatePer Action
Macro or linkNo system access
Custom automationYou build auth
Structured inputs
CommunicateRequired fields
Macro or linkFree-form
Custom automationYou validate
Human fallback
CommunicateSame Inbox
Macro or linkNew ticket
Custom automationYou build routing
FAQ
Questions about what an Agent may do.
Keep the permission model narrow and understandable.
READY WHEN YOU ARE
Turn a repeated support step into an approved Action.
Choose a task your team already handles the same way, set its boundary, and test the result.
One-time $1 activation · Grounded answers · Human takeover · Cancel anytime