A client whose email is down wants to talk to someone now. Your Bot answers as your help desk, takes the company, the person, what is broken and how many people it affects, and marks the ones your rules call an outage.
Made for: Managed service providers · IT support companies · Solo IT consultants · Break-fix shops
Whole office offline since 8:10 this morning. Wi-Fi shows connected with no internet. Router has a red light. Nothing changed yesterday that she knows of. Twelve people affected. Told her an outage gets a callback within 30 minutes.
Example. Names and numbers are made up; the format is what every call produces.
An MSP's phone needs more than a message taken. This logs who, what, since when and how many, flags a real outage by your definition, and never asks a client for a password.
More on how this compares: AI receptionist · AI answering service · replacing voicemail.
Read the guide: After-hours calls for a small MSP: triage without waking everyone
Fill in the brackets, paste it into Settings → Standing instructions, and make one test call. Tighten it after a day of real calls.
Want to hear a briefed Bot first? Listen to two real calls.
You are the help desk assistant for [Company], an IT support provider. Support hours: [hours]. After hours: outages get a callback within [time]; everything else next business day. Outage means: whole office offline, server or email down for everyone, suspected breach or ransomware. Always capture: client company, caller's name and phone, device or service, what they see, when it started, how many people are affected, anything that changed recently. Never ask for or accept a password. Never walk a caller through a fix. If they suspect a breach, tell them to disconnect the machine from the network and wait for the technician.
100 minutes of calls. Then $0.25 a minute.
300 or 1,000 minutes, for a line that's busy all day. Full pricing →
It's a phone number for your Bot. You brief that Bot as your front desk, your sales intake, or both, the way you'd brief a new hire. One line, one Bot, and your instructions, not a generic script.
No. Keep your booking system. The line collects the request and your team confirms it there, or your own Bot books it if you've given it access to that calendar.
No. The line never reads out or takes a card number. Deposits and payments stay in the tools you already use.
No. The line works on its own with standing instructions you write in Settings. If you run Grok Bot, an OpenAI dot, Claude, ChatGPT, or Cursor, connecting it lets your Bot place calls and read every summary itself.
Yes, whenever someone asks. It answers as your business's assistant and never pretends to be a person.
Brief it once. Callers get your business. You get the notes.