Convin Sense

Counts leads per value of one dimension (state, interest, qualification, goal, a custom metric, or AI call disposition) for the campaign_ids given or, with none, every campaign in the organization: the fastest answer to questions about many leads, in one call rather than one per campaign. Metric dimensions count connected leads (answered a call or replied), as on the campaign analytics dashboard, over an optional period on lead creation or activity; disposition counts classified calls over a required call-time period and needs exactly one campaign. Any period spans at most 90 days (calendar days in Asia/Kolkata). Follow up with list_evaluation_reasons for the reasons behind a value.

get_lead_breakdown

A lead's conversation history, newest first: AI and human calls, WhatsApp, SMS and email, each with direction, status, call duration and AI disposition. Answers "what happened with this lead". Open one entry with get_interaction to read the message or transcript.

get_lead_timeline

The connected account in brief: a stable account id, the user's name and email, and a nickname naming the organization. For role, PII masking or granted scopes use get_context instead.

get_profile

One role in full: description, whether it is a built-in system role, how many users hold it, and its permissions grouped by app area with each permission's label and description, next to the catalog permissions it does not grant. Use it to answer what a role can and cannot do; through any role it also shows the complete permissions catalog.

get_role

What one campaign consumed over a period and what it cost, grouped one way at a time. Rows are computed from recorded usage at the plan's current unit prices (the Campaign Costs page's own math), not read from invoices; grouping by metric also attaches the billing provider's invoiced charges for the current billing period, organization-wide, for comparison. Lead charges count leads charged in the period (each lead once, on its first contact attempt or at upload), not leads uploaded, and are gross: the plan's included leads apply to the whole organization per billing cycle. Use it to explain a campaign's bill from activity; for the account state use get_billing. A period spans at most 90 days (calendar days in Asia/Kolkata).

get_usage

The organization's WhatsApp message templates as last recorded from the provider: name, language, category, Meta approval status, quality score and reject reason. Use it to check which templates are approved and sendable, or why one is not. It reads stored statuses and never contacts the provider, and it does not say which campaigns use a template.

list_whatsapp_templates

The organization's AI agents with their languages, channels, voice and whether they are active, most recently updated first. The agent a campaign uses is named in get_campaign. For prompts, opening messages, tools and campaigns use get_agent.

list_agents

The organization's campaigns, most recently updated first, each with lead counts by interest level. Use it to find a campaign id or to compare campaigns at a glance (which have the most hot leads). For one campaign's setup, status and health use get_campaign.

list_campaigns

The reasons the AI recorded for the leads in one bucket of a metric (for example Interest Level = not_interested), newest first with lead ids. Read these to explain why leads landed in a bucket instead of opening leads one by one.

list_evaluation_reasons

Every provider the organization has configured, in one call: messaging (WhatsApp, SMS, email), telephony, the voicebot calling infrastructure, AI models (LLM, TTS, STT) and lead sync, each with its provider, channel, enabled state and whether it runs on Convin's managed account. Contains no credentials, endpoints or settings. Use it to answer which channels or providers are set up and to find an integration id; for the numbers behind telephony and WhatsApp integrations use list_phone_numbers, for WhatsApp templates use list_whatsapp_templates.

list_integrations

The organization's lead stages in funnel order, each with its colour, whether it is an active or terminal stage and whether it is still in use. Read it before filtering or reporting on leads by stage so the stage names you use are the organization's own.

list_lead_stages

AI conversation summaries for many leads of one campaign in one call, most recently active first, each with the lead's state, interest level and last activity. Use it to read what leads are saying at scale. total is capped at 1000. A from/to window on last activity spans at most 90 days.

list_lead_summaries

The bulk lead uploads made to one campaign, newest first: status, file name, who uploaded it, and the total, processed, successful and failed row counts with the upload, start and completion times. Use it to see how many leads were added when and whether an upload is still running or failed; leads added one at a time or through an integration are not listed. Files and download links are never returned. A from/to window on upload time spans at most 90 days.

list_lead_uploads

Every number the organization calls or messages from, in one list: telephony caller ids per telephony integration and WhatsApp business numbers per WhatsApp integration, each with type, status, the integration it belongs to and the campaigns using it (for WhatsApp numbers, the inbound campaigns answering on it). Use it to find which number a campaign dials from, whether a number is in use, or which numbers a provider has. For the integrations themselves use list_integrations.

list_phone_numbers

Every role in the organization, built-in and custom, with its description, how many users hold it, how many permissions it grants and the app modules it hides. Include permissions adds each role's permissions as resource:action pairs, the whole permissions matrix in one call. For one role's permissions with labels, and the catalog permissions it lacks, use get_role.

list_roles

The organization's users with name, email, role and status, plus pending invitations as rows with status invited, newest first. Use it to find who has access, who holds a role, when someone last signed in, or whether a person has been invited yet. For what a role allows use get_role.

list_users

The organization's variable definitions: the keys that prompts, message templates and lead uploads refer to, each with its name, description, data type and whether every lead must have a value. To find one variable, search by its key. Definitions only: a variable's values are never returned.

list_variables

The organization's cloned voices, the custom voices its AI agents can speak with: name, language, gender, provider and whether the voice catalog also shares it with other organizations. Metadata only, never audio. The voice an agent uses is named in list_agents and get_agent.

list_voices

Find leads by an exact identifier (full email address, full phone number or external id), or list them by campaign, state and interest, newest first. Leads cannot be searched by name or by partial values. For counts use get_campaign; for what many leads are saying or why they are not interested use get_lead_breakdown and list_lead_summaries rather than paging. Contact details follow the organization's PII masking.

search_leads