PersuadioAI

Move leads this account owns into a campaign this account owns, by explicit id. Updates membership only: this call sends nothing. But leads moved into an ACTIVE campaign with drip on or Auto Outreach running are texted or emailed on that campaign's next run, with no new review or approval (opt-outs, suppression, quiet hours and caps still apply); do that only when the operator wants those people contacted. Opted-out and suppressed leads are REJECTED with per-lead skip reasons even when listed explicitly; leads already in the target are deduplicated; the response includes the campaign's final lead count read back from the database. To pick the audience by filter instead of by id, use select_and_attach_leads (same attach semantics, driven by search_leads filters). If the target campaign was already reviewed, its earlier approval is stale (the launch step recounts recipients and refuses a token approved for a smaller audience), so a fresh review_campaign_readiness is required before launching.

Summarise the leads in an account or one campaign: how many exist, how many can actually be contacted, how many opted out, and how they break down by status and source. Read-only — sends nothing and changes nothing. Start here when the operator asks what they have to work with.

Attach leads this account owns to a campaign this account owns, by explicit id. Synonym for add_leads_to_campaign — same tool, same behavior, same response shape, just the verb some callers expect. Updates membership only: this call sends nothing. But leads attached to an ACTIVE campaign with drip on or Auto Outreach running are texted or emailed on that campaign's next run, with no new review or approval (opt-outs, suppression, quiet hours and caps still apply); do that only when the operator wants those people contacted. Opted-out and suppressed leads are REJECTED with per-lead skip reasons even when listed explicitly; leads already in the target are deduplicated; the response includes the campaign's final lead count read back from the database. To pick the audience by filter instead of by id, use select_and_attach_leads (same attach semantics, driven by search_leads filters). If the target campaign was already reviewed, its earlier approval is stale (the launch step recounts recipients and refuses a token approved for a smaller audience), so a fresh review_campaign_readiness is required before launching.

Read-only, idempotent campaign readiness status for monitoring and scheduled checks: recipient count, message, channels, cost and every pass/warn/fail check. SENDS NOTHING and NEVER mints an approval token or confirmation phrase, so it cannot launch a campaign. Use review_campaign_readiness only when a human is actively deciding whether to launch.

Copy a previous campaign's configuration (channel, message template, AI instructions, follow-up sequence, sender/automation settings) onto a brand-new campaign, and attach an audience to it. THE RESULT IS ALWAYS A DRAFT — this tool NEVER launches, NEVER sends, and never touches an approval token; it does not call launch_approved_campaign under any circumstance. import_ids (from preview_lead_import / import_leads_from_file) is the preferred way to supply a bulk audience — give several to combine multiple imported files into one campaign; leads are deduplicated across every import_id and lead_id given. At least one of import_ids/lead_ids should normally be supplied, or the clone has no audience. Use channels=['sms'] when the new draft must be text-only with no AI/voice calls, and from_address_id to pin the verified email identity on an email clone. After this, call review_campaign_readiness; only an explicit human approval may lead to launch_approved_campaign.

Create a campaign in draft status with its opening SMS. THIS SENDS NOTHING — a draft cannot deliver a message. It exists so a human can read the exact wording and audience before deciding. The message is rejected if it implies a prior relationship or manufactures urgency. After this, call review_campaign_readiness.

Add a single lead to a campaign this account owns. Requires campaign_id plus at least a phone or an email; deduplicates against the account's existing leads by contact detail. Writes a record only: this call sends nothing. But a lead created in an ACTIVE campaign with drip on or Auto Outreach running is texted or emailed on that campaign's next run, with no new review or approval (opt-outs, suppression, quiet hours and caps still apply). Do that only when the operator wants the person contacted; otherwise use a draft or paused campaign.

Search this account's leads by phone number, email address, or name. Phone matching tolerates formatting differences. Returns masked contact details plus lead ids. Read-only — sends nothing and changes nothing.

Report recorded campaign outcomes: leads, sent records, confirmed delivery receipts, replies, opt-outs, booking records, and AI-paused leads (not people awaiting a human). Omit campaign_id to list campaigns. Account totals are independent of pagination and status filters. Read-only. Null metrics are unavailable; read the caveats before telling the operator a campaign is or is not working.

List the people the Performance page counts as Interested (get_performance_summary engagement.interested: same definition, same campaigns, same window), newest first, with the reply text. Readings come from language-model reply classifiers, a deterministic hot-lead rule, older keyword rows, or the operator's own Interested mark; a STOP, wrong number, no or opt-out never counts. The response names each row's source and includes the reply so you can judge for yourself. Read-only.

The account's performance report, identical to the website's Performance page: pipeline (discovered, purchased, enriched, imported, duplicates excluded), readiness (prepared, approved, eligible at last launch), delivery (queued, provider-accepted, confirmed delivered, failed, unsettled -- never folded together), engagement (replies, interested, appointments, conversions), cost in credits, and one row per autopilot lane. Read-only; sends nothing and buys nothing. A null value means NOT MEASURED and carries an unavailable_reason -- never report it to the operator as zero.

Upsert leads from an uploaded CSV or XLSX file into this account. WRITES TO THE DATABASE — SENDS NOTHING on any channel, ever; this only stores contacts. Deduplicates by phone/email (dedupe_by, default both) against both the file itself and every lead already in this account. Re-importing a lead that is opted-out, suppressed, or do-not-contact NEVER clears those flags and NEVER moves the lead — only genuinely new contacts are created. Returns an import_id: pass it to clone_campaign_draft's import_ids to attach this audience to a campaign. idempotency_key is required — retrying the same key returns the same result rather than importing twice; reusing it with different arguments is rejected as idempotency_conflict.

SENDS REAL MESSAGES TO REAL PEOPLE. This is irreversible and costs credits. It requires an approval_token from review_campaign_readiness and explicit operator authorization for this exact launch. In an interactive current turn where the human explicitly asked to send this campaign, in a session they signed in to themselves (OAuth), pass operator_authorized_this_launch=true instead of asking them to copy/paste the server phrase. With an API key that flag is refused: the operator must type the confirmation phrase. Never set that flag for a scheduled or background run, standing instructions, prior approval, enthusiasm, or inferred intent. Never infer approval. Never generate the confirmation yourself. The exact confirmation phrase remains supported for every client. Never reuse an approval issued for a different campaign or a different size.

The verified email sender identities (from-addresses) this account can send campaigns from. Read-only; sends nothing. Use before an email-channel readiness review to pick the right sender.

Page through this account's leads, optionally filtered by campaign and status. Read-only — sends nothing and changes nothing. For richer filtering (geography, source, tags, contact history, SMS eligibility), use search_leads — the same data with the audience-building filter vocabulary.

Stop a campaign from sending anything further. Queued messages that have not yet gone out are skipped; anything already handed to the carrier cannot be recalled. Safe to call when unsure — pausing is reversible and errs toward not contacting people.

Inspect an uploaded CSV or XLSX lead file WITHOUT writing anything to the database — read-only, sends nothing. Auto-detects common columns (name, phone, email, address, company/entity name) and reports row counts, in-file and account duplicates, missing contact fields, and how many leads would end up SMS- and email-contactable. Run this before import_leads_from_file so the operator can see what would happen first.

Propose how to follow up, based on which leads have never been contacted, were contacted without replying, or already replied. Returns segments with counts and a suggested approach for each. Read-only — this is a proposal to discuss with the operator, not a plan that has been put into effect.

Pre-flight a campaign: how many people would be contacted, on which channels, what it would cost, and which checks pass, warn or fail. SENDS NOTHING. If everything passes, it returns a short-lived approval token and a confirmation phrase — both of which a human operator must authorise before launch_approved_campaign will do anything. Run this before every launch; the token is single-use and campaign-specific.

Search this account's leads by campaign/list, source, geography (city/state/county), lead type, tags, contact history (never_contacted / contacted_no_reply / replied) and SMS eligibility (textable phone, not opted out, not suppressed), with paging and a deterministic sort. Returns lead_id values plus masked contact details and per-lead eligibility flags. Read-only — SENDS NOTHING and changes nothing. This is the filter-rich sibling of list_leads (plain paging) and find_lead (locate one person); use the lead_ids it returns with add_leads_to_campaign, or let select_and_attach_leads run the same filters and attach a bounded subset in one step.

Deterministically select up to requested_count SMS-eligible leads matching the same filters search_leads accepts (nested under 'filters') and attach them to a DRAFT campaign this account owns — the same membership move add_leads_to_campaign performs, driven by a filter instead of an id list. SENDS NOTHING and never launches. Opted-out and suppressed leads are never selected; leads already in the target are skipped. best_eligible orders by score (highest first) then newest, so the same request against the same data selects the same leads; the response lists the exact ids attached, the eligible total, and an honest shortfall when fewer matched than requested. Attaching to a reviewed campaign makes its earlier approval stale (the launch step recounts recipients and refuses a token approved for a smaller audience), so review_campaign_readiness must run again — and then STOP for the human operator.

Rewrite the opening SMS of a campaign that is still a DRAFT. THIS SENDS NOTHING — it changes stored wording only, and it never launches or enqueues anything. DRAFT ONLY: a campaign that has already launched is refused, because editing it mid-send would tell one half of an audience something different from the other; clone it into a new draft instead. The replacement is held to the same rules as create_campaign_draft — 320 characters, and rejected if it implies a prior relationship or manufactures urgency. IT INVALIDATES PRIOR APPROVALS: any approval token issued before the edit stops working, because the launch check covers the message body. Run review_campaign_readiness again afterwards and get a fresh human approval before any launch.