The monitor counts
Minimum sends, minimum reads, all recipients contacted, or a keyword in a report.
List outreach with a plan you approve
Run an objective on a CRM list over WhatsApp, email, or phone. You pick a library template, preview the Organization wallet, then approve the send. Success is sends, reads, or contacted — not a booked appointment.
- CRM query, appointment, or deal audience
- Clarify → approve → send
- Sends, reads, contacted — not Bookings
What it is
A Project-scoped list task: objective, audience, channel, library template, then approve. The planner does not create templates. Adaptive nurture is not shipped.
It does not count
Appointments, pipeline Bookings, or “Interested.” A human or a workflow still moves the card.
Not the inbox bot, not a drip
Three runtimes. They do not share a stop-when-booked contract.
Conversation agent
Live threads in the omnichannel inbox: skills, knowledge bases, router, human handoff.
Growth drip
Clock-based broadcasts. Conversion is reply rate unless you track a pipeline stage.
Autonomous task
Agents → Autonomous. Activity shows the Autonomous tab. Replies still land in Inbox.
- Write the objective Plain language on the Project: who to contact and why. This is not a persona prompt for inbox chat.
- Choose the list CRM query is the usual audience. Appointment query and deal query exist. Campaign-replied and marketplace allocations are not audience sources today.
- Clarify the plan The planner asks for channel and an existing library template. It will not draft, create, or submit a missing WhatsApp template.
- Preview the wallet, then approve Wallet-only pricing: usage meters from the Organization wallet. See pricing. No seat tax for extra tasks.
- Staff the inbox for replies Sends reopen WhatsApp windows when people answer. A conversation agent or RM continues. The task does not become that agent.
What you configure
The product surface is the task, not a vertical clone of a playbook.
Objective
The brief the planner compiles. Playbooks in product are inferred from objective text in places; they are not a hidden closer.
Audience
CRM query, appointment query, or deal query. CSV import is v1 if the list is still a spreadsheet. No marketplace-to-task handoff.
Channels
WhatsApp, email, and phone only for autonomous outbound. Instagram, web chat, RCS, and SMS stay on campaigns, workflows, or inbox.
Library template
You pick an approved artefact. Closed-window WhatsApp is template-only; the planner does not auto-pair session plus template follow-ups.
Success spec
Minimum sends, minimum reads, all contacted, or report keyword. Not appointment booked. Not site visit booked. Not token paid.
Activity
Agents → Activity unifies AI replies, workflow runs, and autonomous tasks so ops can see which runtime fired.
Example: dormant list
The job write-up is cold-buyer win-back. This page is the mechanism.
- Audience400 Dormant contacts on the Project. CRM query, opted-in.
- PlanObjective to re-open them. Approved Gupshup template. WhatsApp and optional email.
- ApprovePreview the Organization wallet, then send.
- After sendMonitor shows sends and reads. Replies hit Inbox. A human or workflow moves Bookings — not the task.
Runtime vs success (one table)
Use this when someone asks the autonomous agent to “just book the visit.”
| Runtime | Trigger | What success means today | Does not mean |
|---|---|---|---|
| Autonomous agent | Approved plan on a list | Sends, reads, contacted, or report keyword | Appointment or site visit booked |
| Conversation agent | Buyer messages inbox / voice | Replies, fields, handoff | A 2,000-row blast |
| Growth campaign / drip | Clock + matched audience | Reply rate labeled conversion | First-class Interested or Bookings |
| Workflow | Event (e.g. stage changed) | The actions you configured | A scheduled list objective |
| Appointments / calendars | Slot confirm on a thread | A real booking | Autonomous monitor output |
Limits
What the product does not do today.
Templates
Pick an existing library item. The planner does not create or submit WhatsApp templates.
WhatsApp window
Closed-window follow-ups are not auto-paired as session plus template.
Audiences
No campaign-reply or marketplace list into the task. CRM, appointment, or deal query.
Channels
WhatsApp (Gupshup), email, phone. SMS is campaigns and workflows when MSG91 is connected.
Analytics
Phone “replied” elsewhere is speech-to-text, not intent. Campaign conversion is reply rate.
Wallet
Preview the Organization wallet before you approve a large list. No seat tax.
Frequently asked questions
Operators wiring Agents → Autonomous for the first time.
Can I set success to “appointment booked” or “site visit booked”?
Not today. Success specs are minimum messages, minimum reads, all recipients contacted, or a report keyword. Move Bookings on the pipeline with a human or a workflow. Appointments and calendars remain the slot truth on live threads.
Will the planner create the WhatsApp template I need?
No. Clarify asks you to choose an existing library template. Submit utility or marketing copy in the library via Gupshup first. AI draft there is text-only; you upload IMAGE headers.
Can the audience be people who replied to last week’s campaign?
Not as an automatic source. Audiences are CRM query, appointment query, or deal query. Campaign engagement and marketplace leads do not flow into autonomous tasks yet.
Is this the same as a Growth drip?
No. Drips are clock sequences with reply-rate conversion. Autonomous tasks take an objective, clarify a plan, and require approve. Neither adapts from last week’s outcomes. Staff the omnichannel inbox for replies either way.
Which channels can a task send on?
WhatsApp, email, and phone. Not Instagram, not web chat, not live SMS. Connect those in Setup → Channels (Gupshup, SES, Plivo). Campaigns support a wider channel set than tasks.
Where do I see runs?
Agents → Activity, Autonomous tab, alongside AI responses and workflow runs. Human handoff still happens in the inbox, not in the task monitor.
Do extra autonomous agents cost seats?
No. Wallet-only pricing. Usage (messages, minutes, AI) meters from the Organization wallet. Details on pricing.
Related product and one example job
Mechanisms here; jobs on playbooks; how-tos on guides.
AI agents
Studio, skills, knowledge, router — the inbox runtime.
Agents →Workflows
Event-driven stage change, CRM properties, start agent.
Workflows →Campaigns & drips
Clock-based sends. Conversion is reply rate today.
Campaigns →Inbox
Where replies and human handoff actually happen.
Inbox →Example job: cold-buyer win-back
Omnichannel playbook — not a vertical clone of this page.
Playbook →Pricing
Organization wallet. Preview before approve.
Pricing →Approve a list plan, then staff the inbox
Connect Gupshup, SES, or Plivo, pick a library template, preview the Organization wallet, and keep Bookings on the pipeline.
Get started free