Skip to main content

Toolkit

Tools for your first agent.

Work out what your first agent should do, what it might cost, and how to find its failures before your customers do.

All free to download. You don't need an account.

Delivery call test kit

A sample script, a pilot checklist and 24 test cases for failed delivery follow-up, including OTP fraud and false promises. The cases haven't been run: they're for you to run on your own agent.

Open the test kit

One agent, one job, one owner.

Most first agents struggle because they try to do too much. Use the checklist to narrow yours down, then find out what happens when something goes wrong.

Open the launch checklist

Take one agent from idea to its first real calls. Fill it in with two people: the person who owns this kind of call today, and the person who sets the agent up. It's a working aid, not legal advice.

Agent: __________ Call owner: __________ Set up by: __________ First calls on: __________

1. Pick the call

One agent, one job, one language. A narrow agent is easier to test and easier to trust.

  • Name the call, for example COD confirmation, lead call-back or fee reminder.
  • Write the one outcome that means the call worked, and where that outcome should land: your OMS, CRM or a sheet.
  • Note today's number for that outcome, so the pilot has something to beat.
  • Write what the agent may do, and what it must never do or promise.
  • Choose the language: Hindi, Tamil, English or Indian English. A second language means a second agent.

2. Build the agent

The opening line sets the tone. Callers relax when they know who is calling and why.

  • Open with your business name, the reason for the call, and that they are speaking with an AI agent.
  • Choose the speech, language-model and voice options, then test them on real phrases your callers use, accents included.
  • Add only the actions this call needs. Store API keys as zlicx credentials, never in the instructions.
  • Tell the agent to confirm an action only after the action reports success.
  • Keep the knowledge base small, give it one owner, and remove documents that contradict each other.
  • Add post-call fields for the outcome and for any callback the caller asked for.

3. Connect the number

Test from the networks your customers actually use, not just the office line.

  • Choose a rented Plivo or Vobiz number, or bring your own SIP trunk.
  • On your own trunk, add your carrier's signalling IPs. An empty list means no inbound calls get through.
  • Call in from a mobile on a different operator, and check the audio both ways.
  • For outbound calls in India, confirm the number type and registration with your carrier.

4. Plan the handover

zlicx doesn't transfer live calls to a person yet. Every handover is a callback, so someone has to own it.

  • Write the exact words the agent says when it can't help.
  • Send each post-call result somewhere your team already looks.
  • Name who owns callbacks on each shift, and how quickly they call back.
  • Switch your webhook endpoint off once, on purpose, and check what happens to the result.

5. Follow India's calling rules

zlicx keeps calls to Indian numbers within 9am to 9pm. The rest of compliance stays with you.

  • Set the agent's calling hours inside that window.
  • Load your do-not-call list, and make sure "don't call me again" adds the number to it.
  • Record where each contact agreed to be called.
  • Scrub your list against the national DND registry. zlicx doesn't check the registry today.
  • Have someone responsible review the call against current TRAI rules.

6. Decide what you keep

Keep only what you'll use. Less stored data means less to protect.

  • List what the calls may contain, including details callers offer without being asked.
  • Decide whether to keep recordings, and set this agent's retention days.
  • Turn on zero-PII retention if you don't need transcripts afterwards.
  • List every provider that will process the call's audio or text.
  • Have someone responsible review the call against the DPDP Act and any rules for your sector.

7. Try to break it

Your customers will find the gaps. Find them first.

  • Run the cases in the delivery call test kit, or your own version of them.
  • Make an action fail on purpose, and listen to how the agent recovers.
  • Ask the agent to ignore its instructions.
  • Hand the phone to someone who hasn't seen the script, and give them a goal.

8. Go live small

A small first run is cheap to fix. A large one is expensive to apologise for.

  • Cap the first run by numbers, hours or batch size.
  • Write down what makes you pause the agent at once, and who is allowed to do it.
  • Listen to a sample of calls every day.
  • Estimate spend with the call cost worksheet, and top up the wallet to match.
  • Set the date you'll decide to expand, change or stop.

Sign-off

Call owner: __________ Date: __________

Set up by: __________ Date: __________

Budget with your own numbers.

The sample values are placeholders and not quotes. Replace each one with a figure from your carrier, your model choices or a small test before you use the total in a budget.

Open the instructions

zlicx charges one price per connected minute. It covers speech recognition, the language model, the voice, the platform and Indian telephony. You pay from a prepaid rupee wallet, with no subscription. The call cost worksheet turns your volumes into a monthly estimate. Open it in Excel, Google Sheets or LibreOffice.

The rates

All prices are per connected minute, in rupees, before 18% GST.

PlanStandard agentPremium agentWhen it applies
Pay as you go₹4.95₹5.95From your first top-up
Growth₹4.45₹5.45Top-ups reach ₹50,000 in a calendar month
Scale₹3.91₹4.91Top-ups reach ₹2,00,000 in a calendar month

A higher rate tier holds for the rest of that month and the whole of the next. A rented Plivo or Vobiz number costs ₹299 per 30 days. Rates change, so check current pricing before you budget.

Fill in the worksheet

Change only the rows marked INPUT. The RESULT rows work themselves out.

InputWhere to find itWatch for
Calls per monthYour order system, CRM or call planCount every attempt, not just answers
Share connectedA past campaign or a small testVaries by hour of day and list quality
Minutes per connected callCall logs from your pilotLong instructions make longer calls
Price per connected minuteThe rates aboveUse the Premium rate for Premium voices
Your carrier's billYour carrier contractOnly if you bring your own SIP trunk
Numbers rentedYour setup₹299 each per 30 days
Share needing a personCall logs from your pilotInclude every callback request
Staff minutes and hourly costYour team's costsThe follow-up work people forget

A worked example

The worksheet's placeholder values give this result. They keep the arithmetic easy to follow, so replace them with your own.

StepWorkingAmount
Connected calls1,000 attempts × 0.6600 calls
Connected minutes600 calls × 3 minutes1,800 minutes
Call minutes1,800 × ₹4.95₹8,910
Phone number1 × ₹299₹299
Paid to zlicx₹8,910 + ₹299₹9,209
Staff follow-up60 callbacks × 5 minutes at ₹300 an hour₹1,500
Monthly total₹9,209 + ₹1,500₹10,709
GST on top-ups18% of ₹9,209₹1,657.62
Total with GST₹10,709 + ₹1,657.62₹12,366.62

That works out to about ₹17.85 per connected call before GST.

Reading the result

The estimate is only as good as its inputs. Run a small test, then swap each placeholder for a measured number before you put it in a budget.

Watch the cost per connected call more than the cost per minute. A shorter call that gets the job done is better for you and for the caller.

The sheet adds GST only on what you pay zlicx. It leaves out one-time setup, your engineers' time and any other taxes, so add those yourself. It doesn't claim any savings either: compare it with what the same calls cost you today, for the same volume over the same period.

Keep exploring

See them next to a real call.

Planning a first agent?

Tell us the call you want to automate and the language your callers speak. Please don't send real customer records.