How to actually use Convarza AI
Every part of the product, written as steps you can follow with the app open beside you. 190 tutorials across 16 sections — start at the beginning, or jump to the thing that is not working.
Start here
8If you have just been given a login, these eight in this order will get you from an empty workspace to something answering customers.
A tour of the workspace: the rail, the top bar and notifications
Where everything lives and, more usefully, why it lives there. Ten minutes here saves a fortnight of hunting through menus for something that was never in them.
ReadAgent, manager and admin: what each role can do
Three roles with different jobs, drawn along one line: agents own their own work, managers own the operation, admins own what costs money or grants access.
ReadConnect your first channel
Adding a channel starts from an icon grid of all thirteen types, not a form. Pick one and its config pane opens immediately, ready to configure.
ReadBuild your first AI bot
An instruction, an opening line, some knowledge, a few functions and a rule for when to fetch a human. You are writing a job description, not a decision tree.
ReadPoint a channel at one thing that answers it
A channel answers with exactly one thing — an AI bot, a call flow, or your agents. Never both, never neither, which is why you always know what picked up.
ReadAssign a conversation and take over from the AI
Assigning is the handover. There is no mode to toggle, no separate bot console, and no conversation being handled by a bot and a person at the same time.
ReadYour first week: a go-live checklist
Eleven checks between a configured workspace and one you can let customers touch. Most bad launches fail one of these, not something exotic.
ReadUnderstand your plan limits and entitlement meters
Minutes, messages, users, channels, automations and storage. What each one actually counts, and the arithmetic that surprises people.
ReadSet up the workspace, learn the vocabulary, connect one channel and get something answering. Start here if you have never opened Convarza AI before.
Create your Convarza AI workspace
Sign up, name the workspace and land on an empty rail. Five minutes, and only two of the decisions are awkward to change later.
ReadA tour of the workspace: the rail, the top bar and notifications
Where everything lives and, more usefully, why it lives there. Ten minutes here saves a fortnight of hunting through menus for something that was never in them.
ReadAgent, manager and admin: what each role can do
Three roles with different jobs, drawn along one line: agents own their own work, managers own the operation, admins own what costs money or grants access.
ReadInvite your team and assign roles
Add the people, give each the narrowest role that lets them work, and tell them what will look broken on their first login.
ReadConnect your first channel
Adding a channel starts from an icon grid of all thirteen types, not a form. Pick one and its config pane opens immediately, ready to configure.
ReadBuild your first AI bot
An instruction, an opening line, some knowledge, a few functions and a rule for when to fetch a human. You are writing a job description, not a decision tree.
ReadPoint a channel at one thing that answers it
A channel answers with exactly one thing — an AI bot, a call flow, or your agents. Never both, never neither, which is why you always know what picked up.
ReadYour first week: a go-live checklist
Eleven checks between a configured workspace and one you can let customers touch. Most bad launches fail one of these, not something exotic.
ReadInstall and use the mobile app
The same workspace on a phone, for the people who are not at a desk. Included on every plan — and worth installing for one reason.
ReadUnderstand your plan limits and entitlement meters
Minutes, messages, users, channels, automations and storage. What each one actually counts, and the arithmetic that surprises people.
ReadStep-by-step connection guides for all thirteen channel types, plus the settings every channel shares — routing, calling hours, health and concurrency.
Add a channel: the icon grid, not a form
Pick a type from a grid of thirteen icons and its config pane opens immediately. Learn the pattern once and all thirteen channels are the same shape.
ReadConnect WhatsApp Business with Facebook sign-in
One click connects the WhatsApp Business account. No credential form to fill in, and the sign-in route configures the webhook for you as well.
ReadConnect WhatsApp Business manually with your own credentials
Manual setup reveals phone number ID, business account ID, secret and app ID, for when your provider needs them by hand. The webhook becomes your job.
ReadConnect Instagram DMs
Instagram is single sign-on only — there are no credential fields, by design. Story replies and DMs arrive as ordinary conversations in the same queue.
ReadConnect a Facebook Page
One sign-in connects the page. Everything a customer sends it arrives in the shared inbox with the contact record beside it, replacing the Pages app for messages.
ReadConnect Telegram with BotFather
Token-based setup, no OAuth dance. A Telegram bot username and its token are the whole prerequisite — and there is one Telegram rule that catches people out.
ReadConnect Viber
Two fields and the channel is connected. Worth having wherever Viber is the default messenger, and identical to every other chat channel once it is in.
ReadConnect LINE
Three values from your LINE official account — bot basic ID, channel token and channel secret — and it joins the same queue as everything else.
ReadInstall the web widget and allow your domains
Copy one embed snippet, allow your domains, and visitors can chat — or start a voice call with your AI agent straight from the page. The fastest channel to get live.
ReadConnect an SMS provider
Typed credential fields — a dial-code select and number for the phone, masked inputs for secrets — and SMS joins the same inbox as everything else.
ReadConnect a shared mailbox as an email channel
The team address — support@, sales@, hello@ — as a channel. Your own personal mailbox is a different thing in a different place, and mixing them up hurts.
ReadConnect Twilio
Point a Twilio number at Convarza and choose what answers it: your agents, an AI voice agent, or a call flow. The numbers and the carrier relationship stay yours.
ReadConnect Maqsam
The same controls every calling channel gets — credentials, a resource picker, region and direction — for teams whose telephony sits with Maqsam.
ReadConnect a SIP trunk for outbound calling
Username, password, port, server domain or IP, protocol and media encryption. Tick Registration if your carrier needs it — it is a checkbox, not a hidden mode.
ReadConnect a SIP inbound gateway
Give the IP or domain of your gateway and pick the protocol. Incoming calls hit your flow or your AI agent — and half the work happens on your gateway, not here.
ReadThe settings every channel has, and the ones only some do
Chat channels and calling channels deliberately do not share controls. Knowing which set you are looking at saves hunting for a field that was never meant to exist.
ReadSet restricted calling hours on a channel
Per-day on/off, Copy Mon→Fri, one timezone and date exceptions. Campaigns inherit them and can only narrow them, never widen them.
ReadRead channel health and fix a disconnection
Most outages are visible on the connection card before customers notice. How to read it, read the whole estate at once, and what breaks per channel type.
ReadSet concurrency with the allowed calls count
How many calls a line may run at once. It belongs to the channel rather than the campaign, which is why a slow campaign is usually a line problem.
ReadFind and use a channel webhook URL
The connection card shows the webhook URL, its verify token and when the last event arrived. It is how a provider tells Convarza that something happened.
ReadAuto-close conversations and control contact creation
Two chat-channel settings that decide how tidy your queue and your contact list stay — and both have a real cost if you set them without thinking.
ReadTemplates, flows, canned messages, payments and the QR code. WhatsApp is the only channel type with its own card, so it gets its own section.
Create and submit a WhatsApp message template
Outside the 24-hour window a template is the only way to start a WhatsApp conversation. Here is how to write one that gets approved the first time.
ReadFix a rejected WhatsApp template
Rejections are almost always one of six things. Work through them in this order rather than rewriting the message from scratch — and rewrite once, not four times.
ReadManage WhatsApp flows
Structured, form-like interactions inside a WhatsApp chat — for the things that genuinely are a form, and not for the things that are a conversation.
ReadSet up canned messages for WhatsApp
The replies your team types forty times a day, saved once. Unlike templates they need no Meta approval, because they only work inside an open conversation.
ReadConfigure WhatsApp payment settings
Take payment inside the conversation where that is available to you, rather than sending people to a link and hoping they come back.
ReadGenerate a wa.me QR code for your number
A QR block with your wa.me link and a downloadable code. Put it where people are standing with a phone already in their hand.
ReadSet the channel message user and broadcast timings
Who outbound WhatsApp appears to come from, and the hours automated messages are allowed to go out. The chat equivalent of restricted calling hours.
ReadShared inbox
13Filters, assignment, the AI badge, notes and mentions, and the activity feed. The daily craft of actually answering people.
The filter chain: All, Sent, Reply, channel, assignee, status
Every filter is a facet on the conversation itself — nothing is a saved search you have to maintain. Learn the chain and you can find anything in two clicks.
ReadFind conversations nobody replied to
The question every manager asks on a Monday, answered with one filter rather than a report — and the two-minute habit that catches leaks before customers do.
ReadAssign a conversation and take over from the AI
Assigning is the handover. There is no mode to toggle, no separate bot console, and no conversation being handled by a bot and a person at the same time.
ReadWhat the AI badge means
One small marker answering the only question that matters at a glance: is a person or a bot talking to this customer right now?
ReadUnassign yourself from a conversation
The one assignment action an agent can take — and what happens to the conversation afterwards is not what most people expect.
ReadReassign work across the team
Managers and admins move conversations and calls through a picker. Contacts and tasks follow a different rule, and knowing which is which saves an argument.
ReadRead the contact record beside a conversation
The person, not just the thread. Everything on the right exists so nobody has to ask the room whether this customer already complained.
ReadLeave a note and mention a teammate
Internal context the customer never sees, attached to the person rather than living in somebody's memory or a private chat.
ReadCreate a task from a conversation
A task created from a chat is auto-assigned to you with a 15-minute reminder and opens expanded — the defaults assume you meant to do it soon.
ReadBook a meeting from a conversation
Put a slot in the calendar without leaving the thread, using availability that reflects your calendar.
ReadThe activity feed: everything that ever happened, in order
Chats, calls, AI tasks, meetings, stage changes, assignee changes, comments and captured form submissions on one filterable feed.
ReadOpen, closed, and what "done" means for your team
The filter most teams set up wrong, because nobody agreed what closed means before they started using it.
ReadTalk to your team without leaving the conversation
Notes, mentions and internal chat exist so "does anyone know about this customer" does not have to happen in a different app.
ReadAI bots
17Prompt, first message, model, voices, functions, knowledge bases, handover conditions and bot flows — for both chat bots and call bots.
Chat bot or call bot: pick the kind when you create it
Same place, same parts, one decision you make at creation and cannot change afterwards. A call bot needs two things a chat bot has no use for.
ReadWrite the instruction for an agent that talks to customers
Not prompt engineering — job description writing. Scope, tone, refusals, and the few sentences that prevent most embarrassing transcripts.
ReadWrite the first message
The exact line it opens with. It shapes the conversation more than the instruction does, because it decides what people ask next.
ReadChoose the model for a bot
Set per bot, on purpose. A deflection bot and a qualifier do not need the same thing — and the more capable model is not always the better one.
ReadSet a voice per language on a call bot
One agent, right accent. Voice lives on the bot — never on a campaign or a channel — and the tier you get depends on your plan.
ReadGive a bot functions it can call mid-conversation
What it may actually do rather than just say — look something up, create a record, offer a slot. Functions are where a bot stops being a FAQ.
ReadLet a bot book a calendar slot mid-conversation
An agent that offers a slot it cannot hold is worse than one that takes a message. Here is everything that has to be true first.
ReadBuild a knowledge base from PDFs and documents
Your help centre was written for people who are already reading it. An agent needs the same facts arranged very differently.
ReadCrawl your website into a knowledge base
Point it at pages you already maintain — and understand that the index is a snapshot, not a live mirror.
ReadReuse one knowledge base across several bots
One base, many bots. It is why your prices only have to be right in one place — and why the Used-by list matters.
ReadWrite handover conditions
The bot's job includes knowing when it is done. Most disappointing deployments fail at the seam, not at the answer.
ReadChoose where a handover goes
A live agent, an AI call, a human with a summary, or a guardrail. Picking the right one is the difference between a rescue and a second failure.
ReadChain bots into a bot flow
Bots in order, each step carrying the condition that passes to the next. A greeter that qualifies, then a specialist that books.
ReadTest a bot before you point a channel at it
Fifteen minutes of deliberate testing prevents the transcript you have to apologise for. Here is the checklist worth running every time.
ReadRead the Used by list before you change anything
Every bot, flow and knowledge base shows what depends on it. Reuse without fear is only possible because of this.
ReadSet call timings on a call bot
When a call bot is permitted to be on a call. Related to, but not the same as, the calling hours on the channel.
ReadStop your bot inventing things
A confident wrong answer is the single most damaging thing an AI agent can do. Six settings and one sentence prevent nearly all of it.
ReadCall flows
11The seven steps, and how to arrange them into flows you can read out loud — IVR menus, business hours, voicemail, conditions and nesting.
Create your first call flow
A call flow is not a programming environment. It is a short list of things that can happen to a call, arranged in the order they should happen.
ReadThe step vocabulary: everything a call flow can do
Ring agents, AI call bot, nested call flow, IVR menu, business hours, voicemail, hang up — plus conditions. That is the entire language.
ReadRing agents: put the call through to people
The step that reaches humans, the rules that decide which humans, and the one thing you must always put underneath it.
ReadHand a call to an AI voice agent mid-flow
The step that turns an unanswered call into a conversation instead of a voicemail nobody listens to.
ReadBuild an IVR menu
The classic press-1 tree, when it helps. Often an AI agent that asks is better — here is how to tell which you have.
ReadBranch on business hours
The step that belongs at the top of nearly every flow, reading the hours the channel already knows.
ReadTake voicemail onto the contact timeline
A message that lands where somebody will see it — on the contact, beside everything else that ever happened.
ReadAdd condition branches to a flow
If and else-if branches, each with its own chain of steps. First match wins, top to bottom — which is the whole rule.
ReadNest one call flow inside another
Build once, reuse everywhere. The reason a single after-hours flow can sit behind six numbers without being copied six times.
ReadSee what depends on a flow before you edit it
Every flow tells you what depends on it — channels and prompt flows both — which is the only reason sharing a flow between six numbers is safe.
ReadBuild an after-hours flow behind several numbers
A worked example, end to end. The calls you miss between 7pm and 9am have a floor of zero, which makes them the safest place to start with AI.
ReadThe calling list, the call logger, the eight outcomes and exactly what each one does to a lead stage.
The calling list: what "to call" means
Every contact assigned to you, whose lead stage is still open, that you have not called today. Three clauses, and the list maintains itself.
ReadMake a call from Convarza
Dial from the calling list, from a contact, or from the keypad — with the record in front of you rather than a number on a sticky note.
ReadLog a call outcome
The dropdown tells you what saving will do before you commit. The label, the colour and the effect all come from one table, so they cannot drift apart.
ReadThe eight call outcomes and what each one does
The whole table, and the consequence attached to each. Learn this once and your pipeline reports will reconcile forever.
ReadWork a list with Save & next
Log the outcome, apply its effect, advance. The whole reason a calling session does not turn into an admin session.
ReadCreate a callback from a call
The one outcome that schedules something. Choosing it creates a task at the time you set, so a promise becomes an obligation with a name on it.
ReadToday: why nobody gets called twice
A small feature that quietly prevents the single most damaging thing an outbound team can do to a customer.
ReadFilter the calling list
Two filters only — assignee and lead stage — and one of them only appears if you manage people. The restraint is deliberate.
ReadFind and play a call recording
Recordings sit with the call, on the contact timeline, where the rest of the story already is — and they are the fastest way to improve an AI agent.
ReadRead a call log entry on the contact timeline
Every attempt — by a person or by a campaign — lands on the feed. It is how "why is this customer annoyed" becomes answerable in ten seconds.
ReadCampaigns
10Pick a line, pick who answers, build the audience and write the follow-up sequence in sentences rather than retry counters.
Create an outbound calling campaign
Four decisions: the line, who answers, the audience and the sequence. Everything a campaign could duplicate from elsewhere has been left where it already lives.
ReadChoose the line a campaign dials on
Only calling channels with outgoing enabled — and the line you pick decides your hours, your concurrency and, more than anything, your answer rate.
ReadChoose who answers for a campaign
An AI bot or a call flow — the same two-way choice a channel makes. The bot owns everything about how it sounds.
ReadBuild a campaign audience
A dynamic filter, a static list, or an import. The choice between them matters far more than people expect.
ReadWrite the follow-up sequence in plain English
A text box, in sentences. There is no retry-after field and no max-attempts counter, because nobody briefs a new agent that way.
ReadOverride calling hours for one campaign
Hours come from the channel by default. A campaign can narrow them for itself, and reset back — but it can never widen them.
ReadRead campaign metrics
Dial attempts, connect rate, meetings booked and progress — and how to tell a list problem from a script problem.
ReadHow campaign outcomes move lead stages
A campaign uses the same outcome table a person does, which is why campaign results and pipeline reports agree without reconciliation.
ReadPause, resume and stop a campaign
What to do when something is wrong, what happens to contacts mid-sequence, and why pausing beats deleting.
ReadWhy a campaign is always outbound
There is no direction control, because a campaign that waits for the phone to ring is just a channel.
ReadWhen this happens, only if, then in order. Triggers, conditions, steps, owners, the Live toggle, catch hooks and time holds.
Create a workflow
Three blocks and you are done. If an automation cannot be read out loud in a stand-up, nobody will trust it enough to leave it on.
ReadChoose a trigger: when this happens
One event starts a workflow, and picking the right one is most of the work. Earlier triggers make shorter workflows.
ReadNarrow a workflow with "only if"
The optional block that stops a good automation firing in the wrong situation — and the cheapest way to control what an automation costs.
ReadAdd steps that run in order
Numbered steps, top to bottom. The order is the logic — and a delay can live inside a step rather than needing its own block.
ReadAssign a conversation automatically
The step that turns unassigned bot traffic into somebody's named responsibility — and, because assignment is the handover, takes the bot off it.
ReadSend a message from a workflow
The customer-facing step. Powerful, metered, and the one most likely to embarrass you if the condition is loose.
ReadCreate a task from a workflow
The step that turns a system event into a human obligation with a name and a due time on it.
ReadMove a lead stage automatically
Useful and dangerous in equal measure. A stage is a claim about a person, so automate it only where the claim is genuinely true.
ReadNotify someone from a workflow
Tell a person that something needs them, without making it their task — and without training them to ignore you.
ReadSet a workflow owner and handle failures
Every workflow has an owner, precisely so a broken automation is somebody's problem rather than nobody's.
ReadUse the Live toggle to test safely
A switch per workflow, so nothing runs by accident. Build them all, turn them on one at a time.
ReadStart a workflow from outside with a catch hook
An inbound webhook: another system posts to a URL and a workflow runs. Available on every plan, and the cleanest way to integrate anything.
ReadMake an automation wait with time-hold
The step that lets a workflow do something later — which is what most genuinely useful automations need.
ReadGenerate a PDF from a workflow
Produce a document automatically — a quote, a confirmation, a summary — and attach it where it belongs. On every plan.
ReadAutomation limits and what counts as an action
Counted per step, not per workflow run. The arithmetic surprises people, so here it is plainly.
ReadLead stages, the seventeen attribute types, filters, bulk edit, import and export — and the three states people most often conflate.
The contact record
Fields, timeline and panels — the thing every conversation, call and campaign writes into, and the reason nothing needs syncing.
ReadCall outcome, lead stage and queue state are three different things
Most CRMs have one status field doing three jobs. That is where reporting goes to die.
ReadLead stages, and which ones are terminal
Six stages take a contact out of the calling list. Knowing which six is the difference between a clean pipeline and a mystery.
ReadCreate a contact quickly
A record-style sheet with one field per row and every attribute directly typeable. Tick Create another and the sheet stays open.
ReadDefine your contact schema: the seventeen attribute types
An admin defines what a contact is, in one editor. Everything downstream reads that schema — the record, the grid, the create sheet and the export.
ReadMake an attribute required or admin-only
Two settings that decide whether data gets captured at all, and who is allowed to see it.
ReadStandard versus custom attributes
What you can change about the fields that shipped with the product, and what you deliberately cannot.
ReadDelete a custom attribute safely
A two-step confirm that tells you how many contacts lose the value. Read the number before you agree with it.
ReadBuild an advanced filter
The same builder used for saved views, exports and campaign audiences. Learn it once and it pays off in four places.
ReadSave a view and share it
A filter you named. It keeps the definition, not the result, so it is right every time you open it.
ReadBulk edit contacts
Change many records at once. Fast, useful, and the easiest way in the product to make a large mistake.
ReadImport contacts from a spreadsheet
The fastest way to fill a workspace, and the fastest way to fill it with duplicates and undialable numbers. Ten minutes of preparation prevents both.
ReadExport contacts to Excel
Always an Excel workbook. Scope it to everything, the current segment, or a custom rule set — and optionally add a second sheet of activity history.
ReadChoose the columns in the contact grid
The column picker is built from your schema, so the grid can show anything a contact holds.
ReadRead the audit trail on a contact
Stage and assignee changes are entries on the activity feed, not silent edits. You can always see who moved what, and when.
ReadConnect Google or Microsoft, publish a booking link with real availability, and let an AI voice agent book straight into it.
Connect a Google calendar
Connecting always routes to one place in settings — never a second connect flow. Do it before you build anything that offers a slot.
ReadConnect a Microsoft calendar
The same place, the same filtering, the same result. Microsoft and Google sit alongside your Convarza calendar.
ReadFilter which calendars you see
One popover, with search, per-account all or none, and a colour per calendar. A small feature with a large effect on a busy week.
ReadMonth, week and day views
Week and day are real time grids — hour rows, events positioned by start and duration, overlaps cascading so labels stay readable.
ReadCreate a booking link
Booking links open from the calendar header. They live inside your calendar, because that is the only place their availability can honestly come from.
ReadChoose how hosts are assigned
Three ways to share a slot, and the reason the third only appears sometimes.
ReadSet weekly availability and timezone
The same hours editor as channel calling hours. One vocabulary, learned once, used in two places.
ReadLeast notice, how far out, and the daily cap
Three settings that stop a booking link ruining a week. The one everybody skips is least notice.
ReadSet the conflict rule on a booking link
What counts as busy. It decides whether a tentative meeting or an all-day event blocks a slot.
ReadAdd a video link or an address to a booking link
Where the meeting happens, decided once on the link rather than typed into every invitation.
ReadBooking links as an agent
An agent can create a link that hosts only themselves. Adding other people is a manager or admin action — and the page says so rather than hiding the control.
ReadCreate tasks from a conversation, a call or a workflow, set reminders, and work the list without anything going quiet.
Create a task
A promise with a name and a time on it. Tasks are records rather than workload, which changes who is allowed to assign them.
ReadTask reminders and the 15-minute default
The 15-minute default is right for something you are about to do, and wrong for a real follow-up. Leaving it on a Thursday task teaches you to ignore reminders.
ReadAssign a task to a teammate
Anyone can assign to anyone — unlike conversations. The difference is deliberate and worth understanding.
ReadWork your task list
The filters, the habit, and the one thing that keeps a task list something people trust.
ReadTasks created by bots and workflows
Automation turns an event into somebody's obligation. Useful — until the volume makes the list unreadable, which happens faster than you expect.
ReadDeal with overdue tasks
The number that tells you whether your task list is a tool or a graveyard.
ReadDashboards, widgets, the call and conversation metrics worth watching, and how to get any of it into Excel.
The Home account overview
Spend, capacity and the state of every channel on one screen. The thirty-second check that catches most problems before customers do.
ReadCapacity against the plan: what runs out first
Four meters — AI voice minutes, AI messages, carrier minutes and automation runs — answering one question: what stops you first if volume keeps climbing?
ReadRead the channel estate
Every channel, its kind, its health and its conversation count in one table. The fastest way to find a channel that has quietly died.
ReadRead the lead funnel
Where contacts stop moving, stage by stage, with each conversion shown against the stage above it.
ReadBot versus agent load
How much the bots absorb before a person is needed — and why there is no correct number, only a trend worth watching.
ReadThe call metrics worth watching
Six call metrics that tell you something worth acting on, the order to look at them in, and the popular number that cannot tell you anything at all.
ReadConversation and response metrics
What to measure on the chat side, and why unreplied is the number that matters most.
ReadReport on campaigns
Dials, connects and bookings per campaign — and how to compare two campaigns without fooling yourself.
ReadExport a report to Excel
For the analysis the screens do not do, and for anyone who will only ever believe a spreadsheet.
ReadUsers and the three roles, permissions in detail, billing and entitlement meters, white labelling and the audit trail.
Add, deactivate and remove users
Seats are a plan limit, and a departing colleague leaves work behind in four places. Both are easier handled deliberately than discovered.
ReadWhat a manager can do that an agent cannot
The line is blast radius: a manager can change how work arrives for everybody. An agent can only change their own.
ReadWhat only an admin can do
Money and access. Everything an admin exclusively controls either costs something or lets somebody in.
ReadBilling: change plan, see usage, manage payment
One pane holds the subscription, the change plan tier, the payment method, the usage summary and cancellation. No exit interview.
ReadUnderstand and top up your calling balance
Real money for carrier minutes and AI voice, shown in currency rather than as an allowance. It is the one number that can stop your phones outright.
ReadChange your payment method
A two-minute job that becomes a service interruption if you leave it until the card has already expired.
ReadCancel your subscription
From inside the product, on the same pane as everything else. But there are four things to do first, and none of them is optional.
ReadWhite label your workspace
Available on Growth and Scaler. Put your own brand on the product your team and your customers see.
ReadAdvanced process settings
Available from Pro upwards. The controls for teams whose process has outgrown the defaults.
ReadBuild and use forms
Structured capture that writes into your contact schema, and lands on the activity feed where somebody will see it.
ReadStorage: what uses it and what to do when it fills
2GB on Starter up to 120GB on Scaler, shared between knowledge bases, files, generated documents and recordings.
ReadYour own account settings
The settings that are yours rather than the workspace's — and the one people most often confuse with a channel.
ReadTwo-factor authentication and active sessions
Two controls under Personal settings that matter far more for admins than for anybody else.
ReadConnect your personal mailbox
Two email syncs per user on every plan. Your one-to-one mail, alongside the conversations rather than in another tab.
ReadNotifications and the notification feed
The one place that tells you something needs you, rather than waiting for you to look.
ReadConsent, DND and the checks before you dial at volume
An autodialler will happily break rules you have not read. What to confirm before the first campaign goes out — not after.
ReadZapier, Make and Integrately, inbound catch hooks, channel webhooks and the developer API.
Connect Zapier
The easiest way to make something outside Convarza react to something inside it, or the reverse. On every plan.
ReadConnect Make
For the integrations with branching and multiple steps that a linear Zap makes awkward. Included on every plan.
ReadConnect Integrately
The third supported option, on every plan. Same principles: keep the Convarza half in a workflow.
ReadDeveloper options and the API
For when an integration platform is not enough. Available on every plan, admin-only for the obvious reason.
ReadCatch hooks versus channel webhooks
Two URLs, opposite jobs, endlessly confused. Five minutes here saves a long afternoon.
ReadImport data through the API
For an ongoing feed rather than a one-off spreadsheet. The same rules apply, except nobody is watching this time.
ReadWhen an integration stops working
Six causes account for nearly every broken integration. Work through them in this order.
ReadWritten the way people actually search — by the symptom, not by the feature. Start with what you can see going wrong.
A channel shows as disconnected
Work through it in this order. The cause is almost always something that changed outside Convarza, not inside it.
ReadMessages are not arriving
Outbound working while inbound does not is a specific, common failure with a specific, common cause.
ReadMy WhatsApp template was rejected
The quick triage, in the order that resolves it fastest — and why you should rewrite once rather than four times.
ReadThe AI bot is not answering
Almost always one of six things, and the first one accounts for most of them.
ReadThe bot answers but never hands over
A bot with no way out is the worst failure mode available, because the customer cannot escape and you cannot see it happening.
ReadCalls are not connecting
Ringing and dropping, refusing to dial, or silent audio — three different symptoms with three different causes.
ReadThe voice agent sounds wrong or speaks the wrong language
Accent, language switching, mispronounced names and awkward pauses each have a different fix.
ReadA campaign is not dialling, or is dialling too slowly
Six causes, ordered by how often they are the answer. Concurrency is usually the one.
ReadA workflow did not run
Read the three blocks out loud first. Most workflow bugs are visible in the definition rather than hidden in a log.
ReadI have hit a plan limit
Which limit you have hit, what it stops working, how to tell from the symptom alone, and the fixes that cost nothing before you consider upgrading.
ReadContacts are duplicating
Four causes, and all of them are much cheaper to prevent than to clean up.
ReadLeads are arriving but nobody is calling them
Almost always one thing: the contacts have no owner. Here is how to confirm it and stop it happening again.
Read