DEV Community: connor gallic

10DLC for Hair Salons, Hairdressers, and Barbers: What You Need to Text Clients

connor gallic — Sat, 07 Nov 2026 15:03:17 +0000

If your salon or barbershop sends texts through an app or phone system, those texts need A2P 10DLC registration. Without it, AT&T, T-Mobile, and Verizon filter them, and clients never see the reminder. Registration tells the carriers who you are (your brand) and what you text about (your campaign). Reminders and confirmations are easy to get approved. Promotions need more. A booth renter with no EIN can still register in their own name.

Most stylists find out about 10DLC the hard way. A client no-shows, says "I never got a reminder," and the booking app says it was sent. This guide covers what you need, in the order you need it.

Which salon texts need 10DLC
Reminders vs. promotions
Booth renters and solo stylists with no EIN
What you need before you start
Sample salon texts that pass review
How clients agree to get texts
Why salon texts get filtered
How KaiCalls handles it
FAQ

Which salon texts need 10DLC

10DLC is about how a text is sent, not what it says. If software sends it from a regular 10-digit business number, it counts. In a salon that usually means:

Appointment confirmations and reminders from your booking app
"Sorry we missed your call" texts from your phone system
"Your stylist is running 15 minutes late" notes sent from the front desk computer
Rebooking nudges ("It has been six weeks since your cut")
Openings and offers sent to a list of clients

What does not need it: a text you type on your personal cell to one client, one at a time. That is person-to-person texting. The moment a tool sends it, or you send the same text to many clients, it is business texting.

One thing to check: some booking apps text from their own shared number, and some text from yours. If the app sends from your number, that number needs to be registered. Ask your app which one it does.

Reminders vs. promotions

The campaign type is the promise you make to carriers about your texts. Get this right and the rest is easy.

Text	Type	Notes
"See you Thursday at 2 PM for color with Maria."	Customer care	Easy to approve
"Reply C to confirm or R to reschedule."	Customer care	Easy to approve
"Sorry I missed your call. Want to book?"	Customer care	The client contacted you first
"Maria is running 10 minutes behind."	Customer care	Easy to approve
"Time for a trim? Book here."	Marketing	Needs a sales campaign and consent
"20% off balayage this week only."	Marketing	Needs a sales campaign and consent
"We had a cancellation at 3 PM today." sent to your list	Marketing	Even though it feels like service

If your texts are only reminders, confirmations, and replies, register for customer care. Review is lighter and consent is simple, since the client booked or called you.

If you also want to send offers and openings to your list, you need a campaign that covers sales texts. Expect closer review. You also need each client's clear permission to get promotions, which is a higher bar than permission to get reminders.

Do not register as customer care and then send promotions. That is the fastest way to get a number filtered or a campaign shut down.

Booth renters and solo stylists with no EIN

Many hairdressers and barbers rent a chair, work under their own name, and never got an EIN. Carriers have a path for that: sole proprietor registration.

You register in your own legal name. No EIN needed.
A personal email is fine.
The carriers text your cell once to check it is really you.
It covers one sending number.

For a solo stylist with one booking number, that is usually all you need. A salon that has its own EIN, several numbers, or several locations should register as a business instead.

What you need before you start

Gather this before you fill out any form. Mismatched details are the top reason brands get rejected.

Your legal name. For a business, use the exact name on your IRS papers, not the salon's nickname. For a sole proprietor, use your own legal name.
EIN, if you have one.
Business address and a contact person with a working email and cell.
A website or booking page that shows your salon's name. Reviewers check it.
A privacy policy that says you will not sell or share client phone numbers for marketing.
Two or three sample texts that match what you will really send (see below).
A short note on how clients agree to get texts (see below).

Brand review often takes one to two business days. Campaign review often takes three to five more.

Sample salon texts that pass review

Reviewers want samples that look like real texts, name your business, and include a way to opt out. Copy and adjust these:

Glow Hair Studio: Hi Jess, you're booked with Maria on Thu 11/12 at 2:00 PM. Reply C to confirm or R to reschedule. Reply STOP to opt out.

Glow Hair Studio: Reminder, your cut is tomorrow at 10:00 AM. Need to change it? Reply here or call us. Reply STOP to opt out.

Glow Hair Studio: Sorry we missed your call. Want to book a time? Just reply with the day that works. Reply STOP to opt out.

If you also send promotions, add one sales sample to a sales campaign:

Glow Hair Studio: We have two openings this Saturday for color. Reply YES to grab one. Reply STOP to opt out.

Keep the samples plain. Skip shortened links like bit.ly, skip all caps, and skip words like "FREE!!!"

How clients agree to get texts

The campaign form asks how people agree to get your texts. Be specific. Vague answers get sent back.

For reminders and replies, consent usually comes from the client:

Booking online and entering their cell number
Calling or texting your salon first
Giving their number at the front desk to get reminders

For promotions, you need a clear yes to marketing texts:

An unchecked box on your booking form that says "Text me salon offers. Msg & data rates may apply. Reply STOP to opt out."
A sign-up text, like "Text JOIN to get openings and offers"

An old client list, a list you bought, or numbers you collected for reminders only do not count as consent for promotions.

Why salon texts get filtered

Even registered numbers can get filtered. The usual causes:

The number is not in an approved campaign. The app says sent. Nothing arrives. Check registration first.
The campaign type does not match. Promotions sent on a customer care campaign.
Shortened links. Use your full booking link instead.
All caps and heavy punctuation. "BOOK NOW!!!" looks like spam.
Late-night texts. Send reminders in the day, not at 11 PM.
Texting people who replied STOP. Once a client opts out, stop until they text START.

How KaiCalls handles it

KaiCalls is a business phone number with a secretary named Kai. Calls ring your cell first. When you cannot pick up because you are mid-color, Kai answers, books the client on your connected calendar or takes a message, and texts them a confirmation. Those texts go out under your salon's own registration.

We file your registration in your salon's name. Carriers require that for texts to your clients. When you sign up, we start the filing from what you already told us. You check it on Dashboard > Compliance > A2P Setup and confirm, and we send it to the carriers. Before we file, we check for common reasons carriers say no, like a PO Box or a website that is only a social page.
No EIN? Booth renters can still register. Tick "I don't have an EIN" and we file you as a sole proprietor in your own name. A personal email is fine. The carriers text your cell once to confirm it is you. It covers one number.
You see every step. Brand review often takes one to two business days and campaign review three to five more. Calls and voicemail work the whole time. Kai starts texting your clients once your campaign is approved. If the carriers send it back, the page shows why, and you fix it and resubmit at no extra charge.
Reminders vs. offers. Pick service texts for reminders, confirmations, and missed-call texts. Pick service and sales texts if you also want to send openings and offers, and only text those to clients who ticked a box to get them. Kai blocks sales language, link shorteners, and all-caps texts on a service campaign. He holds texts between 9 PM and 8 AM in the client's time zone and sends them in the morning. STOP always wins.
Cost. Some plans include registration. On others it is an add-on. See pricing.

The step-by-step is in the text-message registration help page, and the 10DLC registration overview has the short version. For the background, read A2P 10DLC Explained. If you are filing your own campaign, read How to Write an A2P 10DLC Campaign That Gets Approved.

This guide is not legal advice. It explains how carrier registration works so you can ask the right questions.

FAQ

Do hairdressers need 10DLC registration?
Yes, if texts go out through software from a business number. That includes reminders, confirmations, and missed-call texts sent by a booking app, phone system, or answering service. A text you type by hand on your own cell to one client does not need it.

I rent a booth and have no EIN. Can I still register?
Yes. Carriers allow a sole proprietor registration in your own name, without an EIN. The carriers text your cell once to confirm it is you. It covers one sending number.

Are appointment reminders marketing texts?
No. Reminders, confirmations, running-late notes, and replies are customer care texts. Offers and openings sent to your whole list are marketing. They need a sales campaign and the client's permission to get promotions.

How long does salon 10DLC registration take?
Brand review often takes one to two business days. Campaign review often takes three to five more. Plan for about two weeks.

Why do my salon's reminder texts say sent but clients never get them?
Most often the number is not in an approved 10DLC campaign, so carriers filter the texts quietly. Check your registration first. Then check for shortened links and all-caps words.

Hear how Kai books a client. Call the KaiCalls demo line at (417) 835-0402, or start at kaicalls.com.

Your Phone System Is Your Growth Ceiling — Here's How to Remove It

connor gallic — Wed, 04 Nov 2026 15:00:36 +0000

TL;DR: A business cannot convert a call it never answers. Growth creates more phone work: new inquiries, qualification, scheduling, repeated questions, and follow-up. Automating the structured parts of those conversations increases call capacity while keeping people focused on the decisions and relationships that require them.

Why Call Capacity Becomes a Growth Constraint

Marketing can create more demand, but each new inquiry still has to reach someone. When the same small team serves customers and answers every call, busy periods create a simple bottleneck: the phone competes with the work that generates revenue.

Voicemail does not remove that bottleneck. It postpones the conversation and creates a callback queue. A caller with an urgent need may contact the next business instead of waiting.

The cost comparison between AI and human receptionists explains the financial tradeoffs. Capacity is a separate question: can the business answer concurrent and after-hours demand without pulling skilled people away from their work?

Where Humans Matter in the Call Flow

People should remain responsible for moments that need judgment, empathy, negotiation, or authority. Routine intake does not always need the same level of attention.

A structured phone agent can greet the caller, identify the reason for the call, collect required details, answer approved questions, and schedule or route the next step. A person can then enter the conversation with context instead of starting from an empty voicemail.

The AI and human receptionist comparison shows where each approach is strongest. A useful implementation combines them rather than forcing every call into one channel.

Call Records Create Operational Visibility

When calls are answered consistently, they can also be recorded consistently as business events. Transcripts, summaries, lead details, and outcomes reveal what callers ask for and where the current process breaks down.

That record helps a team see recurring questions, gaps in its published information, and calls that still require manual follow-up. The CRM integration guide describes how those records can flow into the systems the team already uses.

Why Voice Automation Is More Useful Now

Modern voice systems combine speech recognition, language models, text-to-speech, and business tools in one real-time conversation. The important improvement is not novelty. It is the ability to understand ordinary language, use current business context, and complete defined actions without forcing callers through a numbered phone tree.

The system still needs testing. Latency, transcription mistakes, missing business facts, and provider failures can all damage a call. A production setup therefore needs monitored test calls, explicit fallbacks, and a fast way to correct the underlying instructions.

The small-business AI receptionist guide covers those capabilities and limitations in more detail.

What Changes When Routine Calls Stop Consuming the Team

Removing routine phone work does not remove people from the business. It changes where they spend their attention.

Staff can receive qualified context before they return a call, focus on active customers, and step in for higher-value conversations. The business can also cover nights, weekends, and simultaneous calls without creating an equivalent increase in receptionist workload.

That is the practical growth argument for automation: not that every call should be handled by AI, but that every caller should reach a deliberate next step.

A Safe First Week

Start with the calls that have the clearest rules, such as after-hours intake or overflow. Confirm the greeting, required questions, scheduling behavior, transfer path, and notifications with controlled calls before widening coverage.

Review the first real conversations. Missing facts and unclear instructions will show up in the transcript. Correct those issues, rerun the affected scenario, and expand only when the evidence supports it.

Related reading: KaiCalls' internally audited production records counted 4,308 calls across 75 configured agents. The companion article, what those records taught us about AI on the phone, separates that evidence from its short embedded video and explains where structured automation helps and where a human should take over.

AI Call Answering Cost Comparison for Law Firms: 2025 Guide

connor gallic — Tue, 03 Nov 2026 15:02:02 +0000

Choosing a call answering solution for your law firm is one of the most consequential decisions affecting both client service and overhead costs. This guide provides a comprehensive comparison of all major options in 2025.

Published by KaiCalls. This October 20, 2026 update corrects KaiCalls allowances and the plan-fit examples against our current pricing. Competitor figures retain their stated research dates and have not been refreshed here; confirm current quotes directly. This is an illustration of published cost models, not a hands-on test, independent ranking or promise of savings.

The Options

1. In-House Receptionist

Hiring a full-time receptionist remains common, but costs have increased significantly.

Costs:

Salary: $35,000-$55,000/year
Benefits (health, PTO, etc.): $10,000-$20,000/year
Payroll taxes: $3,000-$5,000/year
Training and turnover: $2,000-$5,000/year
Total: $50,000-$85,000/year

Limitations:

40 hours/week coverage only
Sick days, vacation, turnover disruptions
Can only handle one call at a time
No after-hours coverage

2. Traditional Answering Services

Human-staffed answering services have been the default "upgrade" from in-house staff.

Examples:

Costs (pricing as of September 2026):

Ruby: $250-$1,725/month (50-500 minutes)
Smith.AI live receptionists: $300-$2,100/month (30-300 calls)
Overage: Smith.AI charges $8.50-$11.50 per extra call; Ruby doesn't publish an overage rate

Limitations:

Per-minute or per-call billing creates unpredictable costs
After-hours coverage limited or premium-priced
Generic scripts (not legal-specific)
Hold times during peak periods

3. AI Call Answering

AI-powered solutions use voice AI to handle calls automatically.

Examples:

KaiCalls
Law Firm AI
Various general AI receptionists

Costs:

KaiCalls: $10/month (Kai Backup, ~20 Kai-answered calls/mo), $79/month (Kai Line, ~170), or $349/month (Kai Office, ~800), or a negotiated Custom plan for high-volume/multi-location firms
Flat pricing — no per-minute overage on any plan

Call allowances are approximate fair-use allowances, not unlimited talk time. A call-count match alone does not confirm that a plan covers your usage. Check your actual call length and the current plan details before choosing. Monthly base prices exclude optional services and applicable telecom taxes and fees. Texting registration coverage and meeting minutes differ by plan; connected services need setup and approval.

Before signing up, ask about plan fit for your call count and call length. Existing owners can review their plan and actual usage.

There are no per-minute overage charges. Your plan includes an expected monthly call allowance. If your call volume stays higher, we recommend the next plan and notify you before anything changes. You can choose to keep your current plan, and we move you back down if volume drops.

Advantages:

Flat-rate predictable pricing
True 24/7/365 coverage
Overflow call coverage
Legal-specific workflows

Detailed Cost Comparison

Ruby and Smith.AI pricing as of September 2026, not rechecked in this update. The examples assume ~3 minutes per call for illustration; this is not a measured average for law firms. KaiCalls rows show base prices and call-count fit, not confirmed quotes for the minute totals. Longer calls can change the plan fit.

Low Volume: 100 Minutes/Month

Option	Monthly Cost	Per-Minute
In-house (prorated)	$4,167	$41.67
Ruby (100 minutes)	$395	$3.95
Smith.AI live (30 calls ~100 min)	$300	~$3.00
KaiCalls Kai Line (call-count fit)	$79 base; confirm usage	Not billed per minute

KaiCalls plan fit: 100 minutes is about 33 calls at the illustrative 3-minute length. That is within Kai Line's approximate 170 Kai-answered calls per month. Confirm your expected usage and setup needs before selecting the plan.

Medium Volume: 500 Minutes/Month

Option	Monthly Cost	Per-Minute
In-house (prorated)	$4,167	$8.33
Ruby (500 minutes)	$1,725	$3.45
Smith.AI live (90-call plan + 77 extra calls ≈ 167 calls)	$810 + $808.50 = $1,618.50	~$3.24
KaiCalls Kai Line (call-count fit only)	$79 base; confirm 500-minute usage	Not a confirmed total

KaiCalls plan fit: 500 minutes is about 167 calls at the illustrative 3-minute length. That call count fits Kai Line's approximate 170-call allowance, so 167 calls alone does not justify recommending Kai Office. However, 500 minutes exceeds Kai Line's underlying 408-minute usage budget. Do not assume that the $79 base price covers this workload. Confirm the plan for your actual call lengths and usage before choosing; a higher plan may be appropriate. Any recommended plan change comes with notice, and you can decline it.

High Volume: 2,000 Minutes/Month

Option	Monthly Cost	Per-Minute
In-house (1.5 FTE)	$7,500	$3.75
Ruby (500-minute plan + overage)	$1,725 + overage (rate not published)	—
Smith.AI (cannot scale)	Not practical	—
KaiCalls Kai Office (call-count fit only)	$349 base; confirm 2,000-minute usage	Not a confirmed total

KaiCalls plan fit: 2,000 minutes is about 667 calls at the illustrative 3-minute length. That is below Kai Office's approximate 800-call allowance, but above its underlying 1,920-minute usage budget. Confirm the plan for actual usage rather than treating the call-count match as a quote or assuming Custom is required.

Hidden Costs to Consider

1. Billing Increments

Ruby: Bills in 30-second increments. A 10-second call is billed as 30 seconds.
Smith.AI: Bills per call regardless of duration. A 30-second call costs the same as a 10-minute call.
AI Services: Most bill per second or per minute with no rounding.

Impact: With 30-second billing, short spam calls and wrong numbers inflate costs significantly.

2. Spam and Robocalls

The average business receives 15-50 spam calls per day.

Traditional services: You pay full price for every spam call.
AI services: Most bill flat-rate, so spam calls don't add to your bill.

Impact: At 30 spam calls/day × $3/call = $2,700/month in wasted spend with traditional services.

3. Add-On Fees

Smith.AI charges extra for (pricing as of September 2026):

Bilingual Spanish: +$1.00/call
Appointment booking: +$1.50/call
Call recording: +$0.25/call
Payment collection: +$1.00/call

Impact: A call requiring Spanish + booking + recording costs an extra $2.75.

AI services: Most include all features in base pricing.

4. Setup and Cancellation

Some services charge:

Setup fees: $100-$500
Early cancellation: 1-3 months penalty
Account changes: Per-modification fees

AI services: Most offer no setup fees and month-to-month billing.

5. After-Hours Premiums

Traditional services often charge:

After 6 PM: 25-50% premium
Weekends: 50-100% premium
Holidays: 100-200% premium

AI services: Same rate 24/7/365.

Impact: A firm receiving 25% of calls after hours pays significantly more with traditional services.

ROI Calculator

Input Your Numbers:

Use these benchmarks to estimate your costs:

Your Metric	Low Estimate	Medium	High
Monthly call minutes	100	500	2,000
After-hours percentage	15%	25%	40%
Spam call percentage	10%	20%	30%
Calls requiring booking	20%	35%	50%

Sample ROI Calculation

Firm Profile:

500 minutes/month
25% after-hours
20% spam calls
35% need booking

Traditional Service (Ruby) Annual Cost (pricing as of September 2026):

Base: $1,725/month × 12 = $20,700 (500-minute plan)
Spam waste: ~$1,200/year
After-hours premium: none published (Ruby states no extra fees for coverage during certain periods)
Total: ~$21,900/year

AI Service (KaiCalls) Annual Cost:

Kai Line base-price illustration: $79/month × 12 = $948, using monthly billing for 12 months, not an annual-prepayment offer
The sample's ~167 calls fit Kai Line's approximate 170-call allowance, but its 500 minutes exceed the plan's 408-minute usage budget; confirm a suitable plan first
Optional services and applicable telecom taxes and fees are additional
$948 is a base-price illustration, not a confirmed annual total for this sample or a savings forecast

Calculate any annual difference only after confirming a KaiCalls plan for your actual usage and obtaining a current competitor quote. The historical Ruby example above has not been revalidated in this update.

Making the Decision

Choose In-House When:

You need a receptionist for non-phone duties (greeting, mail, etc.)
Call volume is extremely low (<50 minutes/month)
You highly value the human presence in your office

Choose Traditional Services When:

You specifically need human operators for complex situations
Your clients specifically request human interaction
You're willing to pay premium prices for perceived prestige

Choose AI When:

You want predictable, flat-rate pricing
After-hours coverage is important
You receive moderate to high call volume
Integration with legal software matters
You want to minimize overhead while maximizing coverage

The Verdict

For most law firms in 2025, AI call answering provides the best combination of:

Coverage: 24/7/365 without gaps or premiums
Cost: compare a confirmed plan for your actual call volume and call length with current quotes from the other providers; these examples do not establish a percentage saving
Quality: Consistent, legal-specific intake
Integration: Deep CRM connectivity

The firms gaining competitive advantage are those capturing leads around the clock while competitors send calls to voicemail or pay premium rates for limited after-hours human coverage.

Ready to see the savings? Try the free demo or compare specific services: vs Ruby | vs Smith.AI

Ruby Receptionist Alternatives: 5 Options Compared (2026)

connor gallic — Mon, 02 Nov 2026 15:02:22 +0000

Consider KaiCalls when you want a business number with a secretary covering the calls your team cannot take. Compare Goodcall if unique-customer billing fits your traffic. If you want people answering calls, compare Smith.ai, Abby, and Moneypenny with Ruby's live service.

If you are looking for a Ruby alternative, start with the part of your current setup you want to change. A lower bill, a different intake process, and more control over who answers are three different buying decisions.

Ruby already publishes 24/7 live answering and English-Spanish call handling. The useful comparison is what happens during your calls, what reaches your team afterward, and what that workload costs.

Which Ruby alternative should you shortlist?

Alternative	Consider it for…	The question to settle before switching
KaiCalls	Team-first answering with a secretary for missed, busy, and after-hours calls	Does the intake and handoff match how your team works?
Smith.ai	Live reception, qualification, booking, and follow-up	Which answering model is in the quote, and what does each call include?
Goodcall	AI answering billed by unique customers	How many different callers contact you each month?
Abby	A dedicated receptionist team with human and AI options	Which calls should go to the team, and which can use AI?
Moneypenny, formerly VoiceNation	Human answering, message delivery, and transfers	What script, coverage, and usage terms apply to your account?

KaiCalls publishes this guide. The shortlist reflects different use cases rather than a hands-on ranking. Descriptions were checked against the official sources linked below on October 22, 2026.

Decide what you need the replacement to do

Review a recent week of calls before requesting quotes. Separate new inquiries, existing customers, booking requests, and calls that must reach a specific person. Then choose the answering pattern: your team first, a receptionist first, or coverage only when you are unavailable.

That choice changes the comparison. If callers need routine answers and booking, a configured secretary may fit. If you want a live person speaking with every caller, start with the human services. If the problem is incomplete notes, test the intake and handoff before assuming a new provider will solve it.

See how KaiCalls handles a call your team cannot take, including the caller details and configured next step. Use that workflow as something to test against your own requirements.

Before a demo, write a short call brief that every provider can use. Include the hours you answer, the calls you want covered, the questions you need asked, and who owns the next step. Keep the same brief for each demo so you can compare the result rather than the presentation.

Separate required work from helpful extras. For example, taking a complete message may be enough for an existing customer. A new inquiry may need screening before anyone offers a consultation. A booking request needs an actual calendar connection and rules for which appointments are available. Put those requirements in writing before comparing a list of features.

Also decide what the service must leave alone. It should know when to stop answering from the business information, when to ask a person, and what to tell a caller if that person is unavailable. A clear boundary is more useful than a promise to handle every possible call. Our small-business answering guide can help you turn those needs into a setup checklist.

Five alternatives, with their practical trade-offs

1. KaiCalls: keep your team first and add a secretary

KaiCalls gives you a business phone with a secretary built in. Your team can answer first; Kai covers missed, busy, or after-hours calls according to your rules. It can answer from your business details, collect caller information, and book through a connected calendar.

You configure the greeting, questions, boundaries, and transfer rules. Your team receives caller context so it can follow through without starting the conversation again.

Choose it when: you want automated coverage around the way your people already answer. If you require a human receptionist on every call, a human service is the closer comparison.

Check the fit: review the actual summary, the unanswered-transfer path, and any calendar or CRM connection you need. Plans have expected answered-call allowances and no per-minute overage charges; business texting requires carrier approval. See current call allowances and texting requirements.

For your test, give Kai a question whose answer is in your business details and another that is outside them. Review the answer and the request left for your team. Then try the configured transfer when the teammate is unavailable. The goal is a usable next step, not simply a call that lasts until the end. Use invented contact details while you learn the controls.

2. Smith.ai: live answering with work around the call

Smith.ai's Virtual Receptionist service lists 24/7 bilingual answering, lead screening, warm transfers, booking, and follow-up. It also offers other answering models.

Choose it when: you want live receptionists handling calls and related tasks such as qualification or booking.

Check the fit: request a quote for the exact answering model you want. Have the provider run your intake and show how the notes, appointment, or follow-up reach your team. A feature list alone does not tell you whether that sequence works for you.

Ask to see the full handoff, not just the receptionist's opening. If a caller meets your screening rules, who creates the appointment or follow-up? If the caller does not meet them, what does the receptionist say and what gets recorded? Ask how your team submits a script change and confirms it is being used. Those answers help distinguish call answering from the extra work you are buying.

3. Goodcall: compare cost by different callers

Goodcall charges for unique customers served rather than call minutes. Its pricing page explains how callers are counted and lists included allowances and additional usage charges.

Choose it when: you want AI answering and your traffic includes repeat callers. Evaluate the billing unit separately from a per-minute or per-call quote.

Check the fit: count different callers, not just total calls. Review current limits for tools, team members, and call history, then test the actions you need. An “unlimited minutes” description does not mean every part of a service is unlimited.

Bring a list of common caller types to the pricing discussion. Ask how the service counts a repeat caller, an unknown number, and calls across a billing period. Check the current terms rather than assuming they work like a minute allowance. Then test the tool or connection needed for your main task. Our Goodcall comparison gives that billing and workflow discussion its own space.

4. Abby: a dedicated team with human and AI options

Abby offers dedicated human receptionist teams, 24/7 reception, bilingual answering, and an AI option.

Choose it when: familiarity with your business and a human receptionist team matter to your caller experience.

Check the fit: decide which calls should reach a person and ask the provider to demonstrate that mix. Confirm coverage, intake, booking, and billing terms for the chosen service rather than relying on an older plan comparison.

Use the same difficult request in both answering options if you are considering a mix. Ask how the handoff works when a caller needs someone beyond the first person or system that answers. Your team should know where to find the note and who needs to act. Confirm who maintains your instructions when opening hours, staffing, or appointment rules change.

The Abby comparison gives you another checklist for the chosen answering model and its handoff requirements.

5. Moneypenny: human answering under the former VoiceNation brand

VoiceNation became part of the Moneypenny brand. Its phone answering service describes answering in your business name, transfers, message delivery, inquiry qualification, and scheduling through integrations.

Choose it when: you want human answering and are comparing message-taking, transfers, and reception tasks.

Check the fit: use Moneypenny's current terms. Ask which workflow and integrations your account includes instead of budgeting from an old VoiceNation price table.

Ask for a demonstration of a transfer that is answered and one that is not. Check the message in each case: it should distinguish a completed handoff from a request waiting for someone. If scheduling is part of your quote, identify the calendar connection and which changes your team must maintain. A familiar service name is not enough to establish what is included in a new agreement.

Compare the bill using your own call mix

A monthly headline price is useful only alongside the work it covers. Ruby's published receptionist plans use minute allowances. Goodcall uses unique customers. KaiCalls uses expected answered-call allowances. Those units are different.

Give each provider the same inputs: total calls, different callers, typical call length, busy periods, and the tasks you expect it to complete. Ask for the resulting monthly cost, including setup, additional usage, integrations, texting, and applicable fees.

A business with frequent calls from the same customers may evaluate unique-customer billing differently from one receiving mostly new inquiries. A long intake also consumes more of a minute allowance than an opening-hours question. Neither pattern is captured by a universal savings percentage.

Our AI versus human receptionist guide explains the staffing choice. The cost comparison gives you more questions to ask when budgeting.

Put the quotes into a simple worksheet. Use a column for the billing unit, the included allowance, extra usage, required connections, setup, and cancellation terms. Keep a separate column for tasks the provider has actually demonstrated. This prevents a lower entry price from hiding a missing task your staff would still need to do.

Ask how billable usage starts and ends. For a minute-based service, confirm how transfers, holds, and brief unwanted calls are treated. For unique-customer billing, ask how caller identity and repeat contacts affect the count. For an answered-call allowance, check which calls count and what happens when expected usage is exceeded. Get the answer from the current quote or terms rather than a comparison article.

Plan for the month you are trying to cover. A regular week may not describe a holiday closure, a busy season, or an advertising campaign. Ask each provider to explain the same workload under its own terms. Do not turn that exercise into a promised savings figure: your call mix and selected tasks determine the result.

Run this test before forwarding customer calls

Use the same three sample calls with each shortlisted service:

A new inquiry: give the caller a question and a reason to book. Check the answer and booking result.
An existing customer: ask for a particular teammate. Test what happens when that person cannot answer.
An unusual request: include something the service should refer to a person rather than answer on its own.

Read what your team receives after each test. Check for a usable phone number, the actual request, and a clear next action. If staff must replay the whole call to understand it, the handoff still needs work.

Record what happened, not just whether the call sounded good

For each sample call, note the question, the answer, the action attempted, and the record your team received. If a booking was promised, check that it exists in the connected calendar. If a person was unavailable, check that the caller was told the actual next step. If something needs a setup change, make it and run the same scenario again before making a decision.

Compare the amount of work left for staff. A tidy message can still omit the reason for the call. A detailed transcript can still lack a clear owner for the next action. Ask the teammate who handles these requests to review the handoff with you. Customer case studies can suggest questions to investigate, but they do not replace that check of your own workflow.

Move the call flow only after the handoff is clear

Keep your current answering arrangement while you configure and assess a replacement. Write down the current number, forwarding arrangement, hours, and people who receive messages. Confirm who controls the number before planning a move. Ask the relevant providers about the steps and timing for any number transfer; do not assume that creating a new account moves it.

If you keep a number customers already call, use the conditional forwarding guide for your carrier. Forward only the calls you do not pick up, according to the coverage you want. A new business number can work without forwarding an old one. Check the arrangement you choose rather than applying a generic phone code.

Finally, name the person responsible for reviewing early handoffs and updating instructions. Keep a clear way to return to the previous call flow if the new setup is incomplete. Confirm cancellation and number-transfer details before ending an existing service. These are questions to settle with the providers involved, not tasks a scripted web preview completes for you.

Questions to settle before switching from Ruby

Does Ruby offer 24/7 service?

Yes. Ruby publishes 24/7 live answering, including weekends, holidays, and English-Spanish call handling. Compare intake, handoff, and usage terms rather than assuming Ruby only covers business hours.

Is an AI secretary a replacement for a human receptionist?

It depends on the calls you want handled. Test routine questions, booking, and routing with the configured secretary. Keep a person available for requests that need judgment or fall outside its instructions. A scripted demonstration does not prove performance on your own calls.

Can my team keep taking calls?

Yes. KaiCalls supports team-first coverage and can handle configured overflow. You choose when to use the secretary; you do not have to hand over every call.

What is the cheapest Ruby alternative?

That depends on your workload and the answering model you need. Compare quotes for the same calls and tasks, including additional usage and optional services. Check current KaiCalls pricing rather than treating an entry price as the cost of any volume.

Try your call flow before you switch

Choose one type of call you want help with and build a KaiCalls preview. Add the business details and questions needed for that call, then test the result your team receives.

A free browser preview is available; live phone service requires payment and setup. Before changing your answering arrangement, check the greeting, intake, transfer fallback, and follow-up. For a closer product comparison, see KaiCalls versus Ruby.

Bilingual Legal Answering Service: 7 Options Compared

connor gallic — Sun, 01 Nov 2026 15:02:17 +0000

Consider KaiCalls if you want a secretary to cover missed calls and follow intake questions you configure. If you want a live receptionist speaking with each caller, compare the human services below. Several offer English-Spanish coverage around the clock; the differences are in the intake, handoff, and billing.

A prospective client calls in Spanish while your team is in court. Someone needs to understand the inquiry, collect the details your firm needs, and make the next step clear. A translated greeting alone does not finish that job.

The right bilingual answering service depends on who you want speaking with callers and what your team needs after the call. Start with those two decisions, then compare coverage and cost.

Which bilingual answering service fits your firm?

Service	Consider it when you need…	What to check in a demo
KaiCalls	Configured English-Spanish intake around your team's own calls	Required questions, caller summary, and transfer fallback
Answering Legal	Live receptionists focused on law-firm calls	Practice-area intake and delivery into your existing workflow
Smith.ai	Live bilingual reception with screening, booking, and follow-up	The answering model in your quote and its handoff rules
LEX Reception	Human legal reception and bilingual client intake	Intake fields, consultation booking, and escalation
Ruby	Live English-Spanish reception for new and existing clients	Intake depth and the receptionist-minute allowance
Abby	A dedicated human receptionist team, with an AI option available	Your preferred human/AI mix and bilingual call handling
Alert Communications	Intake that can extend into retainer coordination	Which intake and retainer tasks the selected service includes

KaiCalls publishes this guide. The shortlist covers different workflows rather than a scored service test. Descriptions were checked against the official pages linked below on October 22, 2026.

Start with the example below if you have not used bilingual intake before. Compare the conversation with the note your team would need to make a useful callback.

Overflow Call Answering Explained: Your Phone Rings First, Kai Takes the Rest

connor gallic — Sat, 31 Oct 2026 15:02:25 +0000

Overflow call answering means your own phone rings first, and a backup answers only the calls you can't get to. You keep the calls you want to take. The ones you miss, because you are busy, on another line, or off the clock, still get answered instead of going to voicemail.

This guide explains how overflow answering works, when a small business needs it, and how to set it up with KaiCalls.

What Is Overflow Call Answering?
When Do You Need Overflow Answering?
How Does Overflow Answering Work With KaiCalls?
Overflow vs. Forwarding Every Call
How Do You Set It Up?
FAQ

What Is Overflow Call Answering?

Overflow answering is a backup for the calls that would otherwise ring out. A call "overflows" when nobody on your team picks up in time. Without overflow answering, that call goes to voicemail or rings until the caller gives up. With it, the call goes to a backup that answers, takes the details, and lets you know.

There are three common triggers for overflow:

Trigger	Example
No answer	You are on a roof and can't reach your phone
Busy	You are already on another call
After hours	The call comes in at 9 PM or on a Sunday

A call center can be the backup, and so can a phone secretary like KaiCalls. Either way, the point is the same: the caller talks to someone, not a beep.

When Do You Need Overflow Answering?

You need overflow answering when you want to take your own calls but can't take all of them. That describes most small businesses:

Owner-operators and trades. Plumbers, HVAC techs, roofers, and appliance repair shops are on jobs most of the day. See appliance repair call answering and after-hours service calls.
Small offices with one front desk. When the person at the desk is on a call, the next caller overflows.
Busy seasons and surges. A storm brings a wave of roofing calls. A heat wave brings HVAC calls. Your team can't take them all at once.
Anyone who hates missing calls but doesn't want to give up the phone. Overflow keeps you in the loop on every call you take, and covers the rest.

If you would rather never answer the phone yourself, you don't need overflow. You can have Kai answer every call instead.

How Does Overflow Answering Work With KaiCalls?

KaiCalls calls this "ring first": your phone rings, and if nobody picks up, Kai answers. Here is the flow:

A customer calls your business number.
Your cell rings first. You can add a few team phones too.
If someone picks up, it is a normal call. Kai stays out of it.
If nobody picks up, Kai answers after about 20 seconds by default. You can change how long your phone rings.
Kai answers by name for your business, asks the questions you set, and takes the message. If your calendar is connected, he can book the appointment.
You get a text with who called and what they need.

Kai answers in English and Spanish, and he sticks to what you tell him about your business. He does not quote prices or make promises you have not given him.

Overflow vs. Forwarding Every Call

Overflow sends only the calls you miss. Forwarding every call sends all of them, and your own phone stops ringing. Pick the one that matches how you work.

	Overflow (ring first)	Forward every call
Your phone rings	Yes, first	No
Who answers when you're free	You	Kai
Who answers when you're busy	Kai	Kai
Best for	Owners who want to take their own calls	Owners who want the phone off their plate

If customers already call an old number, and you want overflow on that number, use conditional forwarding. It sends only the calls you don't answer, are busy for, or can't take. The codes are different on every carrier, and some codes forward every call instead of only the missed ones. Use the call forwarding guide to get the right steps for your carrier.

You can also skip forwarding entirely and use your KaiCalls number as your main line. Ring first works the same way.

How Do You Set It Up?

You can have overflow answering running in a few minutes.

Start here and pick a business number.
Add your cell (and any team phones) as the phones that ring first.
Tell Kai about your business: what you do, your hours, your service area, and the questions to ask every caller.
Make a test call from another phone and let it ring out, so you hear what callers hear.
If you have an old number, set up conditional forwarding with the call forwarding guide.

Compare plans on the pricing page. Every plan has the same features. Plans differ only in how many answered calls and phone lines you get.

FAQ

What is the difference between overflow and an answering service?

An answering service is who answers. Overflow is when they answer. An overflow setup sends a call to the answering service only after your own phone has rung and nobody picked up.

How long does my phone ring before Kai answers?

About 20 seconds by default. You can make it shorter or longer.

Can more than one phone ring first?

Yes. You can add your cell and a few team phones, and Kai answers if none of them pick up.

What happens to after-hours calls?

If nobody picks up, Kai answers, day or night. You get the message by text and can call back when you're ready.

Will callers know it's a backup?

Kai answers by name for your business, on your business number, and takes care of the caller. Callers get an answer instead of voicemail.

Do I need to change my number?

No. You can keep your current number and forward only the calls you miss, or use the KaiCalls number as your main line.

Help Desk Integration for Phone Calls: Turn Support Calls into Zendesk and ServiceNow Tickets

connor gallic — Fri, 30 Oct 2026 15:02:17 +0000

A help desk integration turns each support phone call into a ticket your team already works from. With KaiCalls, Kai answers the call, takes down who called and what they need, and puts it in your help desk. Zendesk Support gets a ticket with a private call note after the call. ServiceNow gets an incident, case or work order while the caller is still on the line. Any other help desk connects through Zapier or a signed webhook.

Email and chat already land in a queue. Phone calls usually don't. The call ends, someone scribbles a note, and the request lives in one person's head until they type it up. This guide covers how to close that gap: the connection options, what lands on the ticket, how to set it up, and how to check it works.

If you send callers to a sales pipeline instead of a support queue, read the CRM integration guide. For the short version of this page, see the help desk integration quick guide.

Why Support Calls Belong in the Help Desk
Four Ways to Connect Calls to a Help Desk
Zendesk Support Integration
ServiceNow Integration
Freshdesk, Help Scout, Intercom and Others
What Lands on the Ticket
Common Help Desk Integration Mistakes
How to Test Your Integration
FAQ

Why Support Calls Belong in the Help Desk

A support call that never becomes a ticket has no owner, no due date and no history. Check three things when you connect phone calls to your help desk:

Every eligible call becomes one ticket. Not zero, not two.
The ticket carries enough to act on. Who called, how to reach them, what they need, and a link back to the call.
Failures are visible. If the help desk rejects a ticket, someone should see it.

A saved call in KaiCalls and a confirmed ticket in your help desk are two separate results. Check both before you rely on the connection.

Four Ways to Connect Calls to a Help Desk

1. Native connection (fastest)

Connect in Dashboard → Settings → Connections. KaiCalls has native connections for Zendesk Support and ServiceNow. An admin approves access once, and tickets follow from real calls.

Best for: teams already on Zendesk or ServiceNow.

2. Zapier (most help desks)

The KaiCalls Zapier app fires on events such as a completed call or a new lead. Pair it with a create-ticket action from your help desk's own Zapier app.

Best for: Freshdesk, Help Scout, Intercom, Jira Service Management and other tools without a native KaiCalls connection.

3. Signed webhooks (most control)

KaiCalls webhooks send signed JSON to your HTTPS endpoint when a call or lead event happens. Your code creates the ticket.

Best for: teams with a developer and a custom ticket format.

4. API (full control)

The KaiCalls API reads calls, transcripts and leads, so you can pull call data into any system on your own schedule.

Best for: internal tools and reporting.

Zendesk Support Integration

The KaiCalls Zendesk integration opens one Zendesk Support ticket for each completed inbound customer call, once a KaiCalls admin turns ticket creation on.

What you need

A KaiCalls business admin
A Zendesk admin to approve access (no API token to paste)
Zendesk Suite, or Support plus Talk Partner Edition
Your Zendesk subdomain (the part before .zendesk.com)

How it works

A customer calls your KaiCalls number. Kai answers and takes the details.
The call ends. KaiCalls checks for an existing ticket with that call's ID, so the same call doesn't open two tickets.
Zendesk gets a ticket on the phone channel with a private note: caller name and number when Kai got them, a short summary, the call time and outcome, whether a transfer was confirmed, and a link to the call record.
If Kai captured a usable email, the caller becomes the ticket requester. If not, their details stay in the note. KaiCalls never makes up an email address.
A receipt in KaiCalls shows whether Zendesk confirmed the ticket.

Setup steps

Open Settings → Connections → Zendesk Support and type your subdomain.
Choose Authorize Zendesk. Your Zendesk admin signs in and approves ticket access.
Pick an optional group, a default priority and tags for new tickets.
Turn on Every completed inbound customer call and save.
Call your line from another phone, then check the receipt in KaiCalls and the ticket in Zendesk.

Limits to know

The automatic policy covers every completed inbound customer call, including sales calls and wrong numbers. There is no support-only filter yet. If your line mixes sales and support, decide that first.
KaiCalls uses your saved group, priority and tags. It does not pick urgency or a group from what the caller says.
The connection has ticket access only. Kai can't read your Help Center articles through it.
Demo calls, test-mode calls and non-customer lines never open tickets.

The Zendesk setup guide has screenshots of each step.

ServiceNow Integration

The ServiceNow connection works during the call, not after it. When a caller reports a problem, Kai can create a record in your ServiceNow instance right then.

What it creates

An incident (the default)
A customer service case
A work order

How it works

Connect your ServiceNow instance in Settings → Connections, with your instance URL and a ServiceNow login or OAuth token that can create the record type you use.
On a call, Kai looks for the caller in ServiceNow by phone number or email.
Kai creates the record with a short description and the call summary. When the caller matches a ServiceNow user on an incident, that user is set as the caller.
If ServiceNow is down or rejects the request, Kai tells the caller plainly instead of promising a ticket that doesn't exist. Login failures mark the connection for attention in KaiCalls.

Best for: IT service desks, facilities teams and field operations that already run on ServiceNow.

Freshdesk, Help Scout, Intercom and Others

There is no native KaiCalls connection for Freshdesk, Help Scout, Intercom, Kustomer, Gladly or Jira Service Management. You can still get calls into them:

KaiCalls event	Where it fires	Example help desk action
`call.completed`	Zapier and webhooks	Create a ticket with the call summary
`lead.created`	Zapier and webhooks	Create or update a contact
`voicemail.received`	Webhooks	Create a ticket from the voicemail

These are plans, not ready-made automations. Check that your help desk's Zapier app or API offers the action you want, map the fields, and test one ticket before you turn it on.

What Lands on the Ticket

Use this as a planning checklist. What reaches your help desk depends on the connection and on what the caller says.

From the call	On the ticket
Caller name	Requester or note
Caller phone number	Note (and phone field, where supported)
Caller email, if given	Requester (Zendesk)
Call summary	Subject and private note
Call time and outcome	Private note
Transfer confirmed or not	Private note
Link to the call record	Private note
KaiCalls call ID	Matching key, so one call opens one ticket

The recording and transcript stay in KaiCalls behind the call-record link. Your team opens them only when they need them.

Common Help Desk Integration Mistakes

1. Sending sales calls to the support queue

A shared line sends every kind of call. If only support calls belong in your help desk, don't turn on the all-calls ticket policy yet. Use a webhook or Zapier filter instead.

2. Auto-replies to callers who never emailed

Help desk triggers often email the requester when a ticket opens. A caller who just hung up may be confused by a "we got your email" reply. Check your triggers before the first test.

3. Duplicate tickets from retries

Networks fail and jobs retry. KaiCalls matches each Zendesk ticket to its call ID, so a retry finds the existing ticket. If you build your own webhook flow, deduplicate on event_id too.

4. No one watching failures

An expired login stops tickets with no noise. KaiCalls marks the connection for attention when the help desk rejects the login. Make sure someone owns that alert.

5. Promising a ticket on the call

Kai should only say a ticket exists when the help desk confirmed it. That's how KaiCalls is built for ServiceNow: anything short of a created record is reported honestly to the caller.

How to Test Your Integration

Call your KaiCalls number from a phone that isn't on your team.
Describe a real-sounding problem and give a callback number.
Hang up and open Settings → Connections. Look for a confirmed receipt.
Open the ticket in your help desk. Compare the name, number and summary with the call record.
Click the call-record link from the ticket and make sure your team can open it.
Call a second time with a sales question, and confirm the ticket policy did what you expected.

Then watch the first few real calls before you stop checking.

FAQ

Which help desks does KaiCalls connect to directly?

Zendesk Support and ServiceNow. Zendesk gets a ticket after each completed inbound customer call once an admin turns ticket creation on. ServiceNow gets an incident, case or work order during the call. Other help desks connect through Zapier or signed webhooks.

Does every call become a Zendesk ticket?

Only after a KaiCalls admin turns it on. A new connection leaves ticket creation off. The automatic policy then covers every completed inbound customer call, including non-support calls.

Can I connect Freshdesk, Help Scout or Intercom?

Not natively. Use the KaiCalls Zapier app or a signed webhook and choose a create-ticket action your help desk offers.

Does the caller get an email when the ticket opens?

KaiCalls adds a private note and does not email the caller. Your help desk rules may send one, so check them first.

Can Kai answer callers from my Zendesk Help Center articles?

Not through the Zendesk connection today. Add your answers to Kai knowledge in KaiCalls instead.

Next Steps

Start with the help desk integration quick guide for a one-page overview, then follow the Zendesk setup guide or the Zapier setup. If your callers are new customers rather than support requests, the CRM integration guide covers HubSpot, Salesforce, Clio and more.

Answering Service for Appliance Repair: Book the Job Before They Call the Next Shop

connor gallic — Thu, 29 Oct 2026 15:02:23 +0000

An appliance repair caller with a dead fridge or a leaking washer usually calls the next shop on the list if nobody picks up. They are not shopping for the best price yet. They want someone who answers, asks the right questions, and gives them a time. An answering service keeps your line covered while you and your techs are on jobs, so that caller books with you.

This guide covers what an appliance repair shop should capture on every call, the options for covering your phone, and how to set up KaiCalls as your phone secretary.

Why Do Appliance Repair Shops Miss So Many Calls?
What Should Get Captured on Every Appliance Repair Call?
What Are the Options for Covering Your Phone?
How Does KaiCalls Handle an Appliance Repair Call?
How Do You Set It Up?
FAQ

Why Do Appliance Repair Shops Miss So Many Calls?

Most appliance repair shops are one to five people, and the person who answers the phone is also the person fixing the dryer. The calls do not wait for a good moment.

You are on a job. Your hands are inside a dishwasher, or you are on a customer's kitchen floor. Stopping to answer looks bad to the customer in front of you.
You are driving. Back-to-back service calls mean a lot of time behind the wheel.
The phone rings after hours. A fridge that stops cooling at 8 PM is a real problem for the family that owns it. They call that night, not the next morning.
Voicemail does not book jobs. Many callers hang up instead of leaving a message, and the ones who do leave one have often booked someone else by the time you call back.

The fix is not to answer every call yourself. It is to make sure every call reaches someone who can take the details and book the visit.

What Should Get Captured on Every Appliance Repair Call?

A good call ends with everything your tech needs to show up with the right part. A name and number is not enough. Use this list:

Detail	Why it matters
Name and callback number	So you can confirm the visit
Service address or ZIP code	So you know it is in your service area
Appliance type	Fridge, washer, dryer, dishwasher, oven, range, microwave, ice maker
Brand	Some shops only service certain brands
Model number, if they have it	So the tech can check parts before the trip
The problem, in their words	"Not cooling", "won't drain", "making a grinding noise"
Error code on the display	Often points straight at the fault
Warranty or home warranty company	Changes who pays and how you bill
Urgency	A leak or a fridge full of food is not the same as a noisy dryer
Best time for a visit	So the booking sticks

Tell callers where to find the model number. On most fridges it is inside the door or on a wall of the fresh food section. On washers and dryers it is usually inside the door or lid. Callers who know where to look can read it off in seconds.

What Are the Options for Covering Your Phone?

There are four common ways an appliance repair shop covers its phone, and they differ in who answers and what the caller gets.

Option	Who answers	What the caller gets
Voicemail	Nobody	A beep. Many hang up.
Office staff	A person on payroll	A real conversation during office hours only
Live answering service	A call center operator	Message-taking, often from a script, billed by the minute or call on many plans
A phone secretary like KaiCalls	Kai, on your own business number	Answers every call, asks your questions, takes the message, and books on your calendar if it is connected

If you already have staff in the office, the right setup is usually "office first, secretary for overflow." Your team takes the calls they can, and the ones they can't still get answered. See how overflow answering works.

How Does KaiCalls Handle an Appliance Repair Call?

KaiCalls rings your cell first, and Kai answers if you don't pick up. Here is what happens on a typical call:

A customer calls your business number about a dryer that won't heat.
Your phone rings first. If you pick up, it is a normal call.
If you don't, Kai answers by name for your shop and asks your questions: address, brand, model number, the problem, and whether it is under warranty.
If your calendar is connected, Kai can offer open times and book the visit. If not, he takes the full message.
You get a text with who called and what they need, so you can call back from the job site with the details in front of you.

Kai answers in English and Spanish. You can tell him which brands you service, your service area, and what to say about trip fees, and he sticks to what you give him. He does not quote prices or promise repairs you have not told him about.

How Do You Set It Up?

You can get a KaiCalls number and have Kai answering in a few minutes.

Start here and pick a business number.
Tell Kai your shop name, the appliances and brands you service, your service area, and your hours.
Add the questions you want asked on every call, using the table above as a starting point.
Choose how calls reach you: ring your cell first, or let Kai answer every call.
If customers already call an old number, forward only the calls you miss to your KaiCalls number. The call forwarding guide has the steps for your carrier.

Compare plans on the pricing page. Every plan has the same features. Plans differ only in how many answered calls and phone lines you get.

FAQ

Do I need an answering service if I only have one or two techs?

Small shops need it most. With one or two people, every minute on the phone is a minute not fixing appliances, and every missed call is a job that may go to another shop.

Can it tell an urgent call from a routine one?

Yes. You tell Kai what counts as urgent for your shop, such as a leak or a fridge that has stopped cooling, and he asks about it on every call and flags it in the message you get.

Can callers book a visit during the call?

Yes, if your calendar is connected. Kai offers open times from your calendar and books the visit. Without a connected calendar, he takes the full message and you book the visit when you call back.

Will callers know they reached my business?

Yes. Kai answers by name for your shop, on your business number.

Does it work after hours and on weekends?

Yes. Kai answers whenever a call comes in, including nights, weekends, and holidays. You set what he tells callers about when you can come out.

Do I have to change my phone number?

No. You can keep your current number and forward only the calls you miss, or use the KaiCalls number as your main line.

KaiCalls for Zendesk: call notes in your support queue

connor gallic — Sat, 24 Oct 2026 15:00:17 +0000

Zendesk has approved the KaiCalls integration. The workflow is built around a practical handoff: the phone call ends, and your support team can pick up the request in Zendesk with the details attached.

Approval is one step. We are still confirming the public Marketplace listing before sharing its link.

Give the next person the context

A support call often needs a second person. They need to know what the caller asked, how to reach them, and what happened during the call.

The KaiCalls connection creates a Zendesk Support ticket after a completed inbound customer call, once your administrator turns ticket creation on. A private note carries the caller details captured, a short summary, the call outcome, and a link to the KaiCalls call record.

Your team can review the call before replying. KaiCalls uses the call ID to check for an existing ticket, and its receipt shows whether the ticket was confirmed in Zendesk.

Keep control of the ticket policy

Connecting a new Zendesk account leaves ticket creation off. You choose the group, default priority, and tags, then save the ticket policy when it fits your line.

The current automatic choice covers every completed inbound customer call. It includes non-support calls. If you only want selected calls to become tickets, leave it off. This version does not have a support-only filter.

That is the first decision to make before connecting a shared sales and support line.

Set it up where your phone is managed

This is a connection inside KaiCalls, with approval from a Zendesk administrator. There is no Zendesk sidebar app to install and no personal API token to paste.

You need a KaiCalls business administrator and Zendesk Suite, or Support plus Talk Partner Edition. The connection requests ticket read and write access. Help Center access is outside this release.

Phone handoffs remain separate from ticket creation. If you will pass callers to a person, test that route with the receiving person as well as checking the ticket.

Start with the Zendesk integration overview and the connection and test guide. For a line that mixes support with other calls, ask for setup help to review the workflow before turning tickets on.

How to Write an A2P 10DLC Campaign That Gets Approved the First Time

connor gallic — Thu, 17 Sep 2026 15:01:19 +0000

Most A2P 10DLC campaign rejections are wording problems, not business problems. The reviewer needs to see four things line up: a campaign type that matches the messages, a description that says plainly who you text and why, sample messages that look like the description and carry opt-out language, and a consent explanation specific enough that they could go verify it themselves. Get those four consistent with each other and approval is routine. Leave one vague and you will wait a week to be told to try again.

This guide is for anyone filling out the campaign form — a business owner registering their own Twilio account, or anyone curious what "we handle registration for you" actually involves. If you use a KaiCalls number you do not need to do this; your number is on KaiCalls' approved campaign already. If you connect your own Twilio account, this is the form you will be filling out, and the KaiCalls dashboard will track your status while you do.

We are writing from experience. KaiCalls' own first campaign submission was sent back for exactly the consent problem described below. What follows is what we changed.

Before the campaign: get the brand right
Choose the campaign type honestly
Write the use-case description
Write sample messages that match
Describe consent so a stranger could verify it
The keyword replies
The rejection reasons that catch almost everyone
After approval: attach the numbers
A pre-submit checklist
FAQ

Before the campaign: get the brand right

The campaign sits under a brand, and the brand is checked against government records. Use the exact legal entity name on your IRS paperwork — not the DBA, not the name on the truck, not the version with "LLC" dropped for style. Use the EIN and the registered address that go with that name. A mismatch here is the single most common brand rejection, and it delays the campaign because you cannot submit one until the brand is approved.

Sole proprietors without an EIN have a separate brand type with lower throughput and a one-number limit. If you have an EIN, use it.

Brand review commonly takes one to two business days.

Choose the campaign type honestly

The campaign type is a promise about what the traffic is. Reviewers compare everything else in the form against it.

Customer Care — replies, confirmations, follow-ups, support, to people who contacted you first. This is the right type for a business that texts callers back, confirms appointments, or answers questions. Lower risk, straightforward consent.
Account Notification — non-promotional updates about an account the person holds.
Marketing — promotions to people who explicitly agreed to marketing. Stricter consent, closer review.
Low Volume Mixed — a catch-all for small senders doing several things. Tempting because it sounds flexible; in practice it invites more scrutiny because "mixed" includes marketing, and the consent bar is set by the strictest thing you might send.

If your texts are really customer care, say Customer Care. Do not pick Mixed as a hedge. It makes the consent description harder and the review slower, and it does not buy you anything you will use.

Write the use-case description

The reviewer reads this first. It should answer, in plain sentences: who receives these texts, what triggers them, what they contain, how often they come, and how to stop them.

A structure that works:

[Business] uses text messages to communicate with customers who have already contacted us by phone or through our website.
Messages are sent only after a customer initiates contact.
Message types include: appointment confirmations, missed-call follow-ups, replies to customer questions, and service updates.
All messages relate directly to a conversation the customer started with us.
Frequency varies by conversation, typically 1–5 messages.
Customers can opt out at any time by replying STOP.

Notice what it does. It names the trigger (customer initiates). It lists concrete message types that all fit Customer Care. It states frequency. It states the opt-out. It does not say "marketing," "campaigns," "promotions," or "outreach" anywhere — those words on a Customer Care form are a flag.

Describe the messages and the recipients, not the technology producing them. Whether a person, a template, or an assistant composes the text is not what the reviewer is evaluating. Whether the traffic matches the use case and whether recipients consented is.

Write sample messages that match

You will be asked for two to five sample messages. Rules that keep them from being the reason you are rejected:

They must look like the description. If you said "appointment confirmations and missed-call follow-ups," the samples should be an appointment confirmation and a missed-call follow-up. A sample that reads like a promotion contradicts the Customer Care type.
Identify the business in the message. Start with who is texting.
Put opt-out language in at least one, ideally all. "Reply STOP to opt out."
Use brackets for variables. Reviewers understand [Name] and [Date].
No shortened links. If you include a link, make it a full branded URL.

Samples in the shape that gets approved:

Hi [Name], this is [Business]. Thanks for calling earlier. If you'd like to continue the conversation, reply here and we'll help you. Reply STOP to opt out.

Hi [Name], your appointment with [Business] is confirmed for [Date] at [Time]. Reply STOP to unsubscribe.

Hi [Name], we missed your call. If you still need help, reply here and we'll get back to you shortly. Reply STOP to opt out.

Hi [Name], following up on your inquiry with [Business]. Let us know if you'd like more information. Reply STOP to unsubscribe.

Four samples, four message types, all four named in the description, all four with opt-out language. That consistency is the whole trick.

Describe consent so a stranger could verify it

This is the field that gets the most rejections, and it is where our own first submission failed. The reviewer's job is to confirm that recipients agreed to receive texts. A sentence like "customers consent when they contact us" is not verifiable. You need to describe each consent path concretely enough that the reviewer could go check.

List every way a person can end up receiving texts from you, and for each one, say exactly what they see or hear:

Web form. Give the URL of the form. State that it has an SMS consent checkbox, that the checkbox is unchecked by default, that checking it is not required to submit the form, and quote the disclosure text next to it verbatim. The disclosure should say who is texting, that frequency varies, that message and data rates may apply, and how to STOP and get HELP. Link the privacy policy and terms from the form and give those URLs too.

Customer-initiated text. State that a person who texts your number first is consenting to a reply about their inquiry, and quote the first automated reply — which should itself include the rates disclosure and STOP/HELP instructions.

Phone call follow-up. State that a caller may receive a follow-up text about their call, quote the notice they hear during the call, and state that consent is logged with the phone number and a timestamp.

Then make sure every URL you cited is live and says what you claimed. Reviewers click. A consent description pointing at a contact form with no checkbox is a rejection.

If you maintain a public page describing your texting program — what people receive, how they opt in, how they opt out, that rates may apply — cite it here too. It is inexpensive to publish and it gives the reviewer one place to verify the whole story.

The keyword replies

You will be asked for the exact text of your opt-in confirmation, opt-out confirmation, and help reply. Keep them short, and make sure they match what your system actually sends.

Opt-in: "You've been subscribed to messages from [Business]. Reply STOP to unsubscribe, HELP for help. Msg & data rates may apply."
Opt-out: "You have been unsubscribed. You will not receive any more messages from this number. Reply START to resubscribe."
Help: "Reply STOP to unsubscribe. Msg & data rates may apply."

Do not leave any of these blank or as a dash. A missing opt-in confirmation was one of the specific line items on our own rejection.

Your system must honor STOP, START, and HELP on every number in the campaign — and the list of words that count should be broad: STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT for opting out; START, YES, UNSTOP for opting back in; HELP, INFO for help. Save the opt-out before you send the confirmation, so you never tell someone they are unsubscribed when the save failed.

The rejection reasons that catch almost everyone

In rough order of frequency:

Consent not verifiable. The description is generic, has no URLs, or points at a page that does not show what it claims. Fix: the section above.
Business details do not match records. Legal name, EIN, or address differs from IRS data. Fix: use the exact legal entity.
Use case too vague. "Marketing" or "customer communication" with no specifics. Fix: name the message types and the trigger.
Samples do not match the use case. A Customer Care campaign with a "20% off this week" sample. Fix: make the samples the message types you listed.
Missing opt-out language in samples. Fix: "Reply STOP to opt out" in each.
Blank keyword fields. Opt-in or help reply left empty. Fix: fill all three.
Wording that reads like marketing on a Customer Care form. "Campaign messages," "outreach," "promotions." Fix: describe replies and follow-ups.

A rejection is not a restart. The reviewer names the item. Fix that item, leave everything else alone, and resubmit.

After approval: attach the numbers

An approved campaign does nothing by itself. Registration attaches to a number through the campaign. In Twilio, every number you want to text from has to be added to the messaging service linked to the campaign. A number outside that service is still unregistered traffic and will be filtered exactly as if you had never registered — error 30034 is the usual signature. If you later buy or port a number, attach it too.

Once your numbers are attached, the KaiCalls A2P Setup page reflects the campaign status, and Kai's texts from those numbers go out as registered traffic. Campaign review commonly takes three to five business days after brand approval. Do not send texts before approval.

A pre-submit checklist

Brand uses the exact legal entity name, EIN, and address on IRS records
Campaign type is Customer Care (unless you actually send marketing)
Description names the trigger, the message types, the frequency, and STOP
Description contains no marketing vocabulary
Two to five samples, each one a message type named in the description
Every sample identifies the business and includes opt-out language
Consent description covers every path, with verbatim disclosure text
Every URL cited is live and shows what the description claims
Web form checkbox is unchecked by default and not required
Opt-in, opt-out, and help replies are all filled in and match what your system sends
Your system honors STOP/START/HELP on every number
Plan to attach every number to the messaging service after approval

FAQ

Which 10DLC campaign type should a small business pick?
If your texts are replies, confirmations, and follow-ups to people who contacted you first, Customer Care. Only pick Marketing or Mixed if you actually send promotions, and expect a stricter consent bar if you do.

Why was my campaign rejected for call to action or opt-in?
The reviewer could not verify how people agree to receive your texts. Describe every consent path with the exact disclosure text and live URLs for the form, privacy policy, and terms.

Do I have to mention AI in my campaign description?
Describe what the messages are and who receives them, not the technology that composes them. Reviewers evaluate use-case fit and consent.

How long does approval take?
Brand review commonly takes one to two business days; campaign review three to five more after that. Plan for up to two weeks end to end and do not schedule a texting launch against the optimistic end.

I use a KaiCalls number. Do I need any of this?
No. Your number is on KaiCalls' approved Customer Care campaign from the moment it is provisioned. This guide is for businesses that connect their own Twilio account, or anyone who wants to understand what the registration involves. See How KaiCalls Handles A2P 10DLC Registration.

Rather skip the form entirely? A KaiCalls number comes registered. Sign up at kaicalls.com, or call the KaiCalls demo line at (417) 386-2898 and ask Kai.

How KaiCalls Handles A2P 10DLC Registration So Your Texts Actually Deliver

connor gallic — Wed, 16 Sep 2026 15:01:50 +0000

KaiCalls registers your number for texting before it goes live. KaiCalls holds an approved A2P 10DLC brand and a Customer Care campaign with the carriers; every KaiCalls number is added to that campaign's sender list when it is provisioned, the number is held if that step fails, the whole pool is re-checked nightly, and any text that cannot be sent from a registered number is routed through a registered sender instead. If you use a KaiCalls number, there is no form to fill out and no waiting period. If you bring your own Twilio account, you register your own brand and campaign and the dashboard tracks your status.

That is the summary. This post is the long version — the actual mechanics, including the parts that are deliberately conservative, because "we handle compliance for you" is a sentence every vendor writes and very few can explain.

If you are new to the topic, start with A2P 10DLC Explained. This post assumes you know what a brand and a campaign are.

The two ways a number can be registered
Why KaiCalls chose a shared Customer Care campaign
Step 1: Enrollment happens before activation
Step 2: Nightly reconciliation
Step 3: Registered sender or nothing
Step 4: The rules enforced in code
What the dashboard shows you
If you bring your own Twilio account
What KaiCalls does not do
FAQ

The two ways a number can be registered

A2P 10DLC registration attaches to a phone number through a campaign. There are two ways a small business ends up with a registered number:

	Register your own	Use a provider's campaign
Who files the brand	You	The provider
Who files the campaign	You	The provider
Wait before texting	1–2 weeks	None
Who is responsible for staying inside the campaign's rules	You	The provider, for every number on it
Best for	Businesses with their own Twilio account or unusual use cases	Businesses that want a number that texts on day one

KaiCalls uses the second model for the numbers it provides. Businesses that connect their own Twilio account use the first. Both are covered below.

Why KaiCalls chose a shared Customer Care campaign

The campaign type is the promise you make to the carriers about what your texts are. KaiCalls' campaign is registered as Customer Care, not Marketing and not Mixed. That was a deliberate choice, and it shapes everything downstream.

Customer Care covers messages to people who have already contacted the business: replying to a missed call, confirming an appointment, continuing a conversation someone started, answering a question. That is a precise description of what Kai does. He is a secretary who texts callers back. He does not run blasts.

The upside of Customer Care is that carriers treat it as low-risk, and consent is straightforward — the customer initiated contact. The cost is that the campaign has rules, and every number on it is bound by them. A single business sending promotional texts from a Customer Care number puts every other number on the campaign at risk. So KaiCalls does not leave those rules to a policy page. They are enforced in the sending pipeline, covered in Step 4.

Step 1: Enrollment happens before activation

When a KaiCalls number is provisioned — at signup, when you buy an extra line, or when a setup call assigns one — the platform immediately adds that number to KaiCalls' registered messaging service, which is the sender pool attached to the approved campaign.

This is a gate, not a background job. If the add fails for any reason, the number is marked as held, it is not activated, and the provisioning step reports the failure instead of pretending it worked. The number waits for reconciliation rather than going live as an unregistered sender.

The reason for that severity is the failure mode it prevents. Before this gate existed, a number could be handed to a business, work perfectly for calls, and silently drop every follow-up text for days because one enrollment call had failed with no one watching. Calls working made the problem invisible. The owner found out from a customer. Making registration a precondition of activation means a number that reaches you is one the carriers already know.

The number pool also prefers already-enrolled numbers when assigning one to a new business, so most signups get a number that was registered before they ever saw it.

Step 2: Nightly reconciliation

Registration state can drift. A number can be removed from a sender pool by an operator, a provider-side hiccup can leave one out, or a number can be moved between services during maintenance.

So every night, a scheduled job pulls the list of every active KaiCalls number, pulls the campaign's actual sender list from the messaging provider, and diffs them. Any active number missing from the campaign is re-enrolled on the spot. A number that is already there is left alone.

This is the boring part, and it is the part that keeps the promise honest over months rather than on the day you signed up.

Step 3: Registered sender or nothing

When Kai sends a text, the platform decides which number it goes from. Ideally that is your business number, so the customer sees the same number they called.

But the sender logic checks a condition first: is this number active and enrolled in the registered campaign? If yes, the text goes out from your number. If no — enrollment is still pending, or the number was held — the text is routed through KaiCalls' registered messaging service rather than sent from the unregistered number.

That means a text that would otherwise have been silently filtered still reaches the customer. It may arrive from a KaiCalls sender instead of your exact number during that window, which is a worse experience than normal. It is a far better experience than the customer never hearing from you and assuming you ignored them. The same check is applied whether Kai sent the text or you typed a reply from the dashboard.

Step 4: The rules enforced in code

A Customer Care campaign stays approved only if the traffic on it looks like customer care. KaiCalls enforces the campaign's rules in the outbound text pipeline, before a message is handed to the carrier. Every outbound text passes through these gates in order:

Valid destination. The number has to be a real, properly formatted phone number.
Content screen. Kai blocks marketing language, URL shorteners, messages over 1,600 characters, and messages that are mostly capital letters. These are the patterns that get Customer Care traffic reclassified as spam. One-time codes and account notices skip the content screen, since they are not conversational.
Consent. The recipient must have a consent record for texts: they called, they texted, or they submitted a web form with a consent box. A number with no consent record does not get a text.
Opt-out and Do Not Call. If the number ever replied STOP, or is on your Do Not Call list, the text is blocked. STOP always wins, even over a newer implied consent.
Quiet hours. Texts between 9 PM and 8 AM in the recipient's local time are held and sent the next morning, not dropped.
Rate limit. A daily cap per business and a per-recipient limit stop bursts.
Send.

Inbound keywords are handled on every number as well. STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, and QUIT mark the number opted out and trigger one confirmation reply. START, YES, SUBSCRIBE, UNSTOP, and OPTIN turn texts back on. HELP, INFO, SUPPORT, and ASSIST get a short help reply. Plain-language requests like "take me off your list" are treated as STOP. And the opt-out is saved before the confirmation is sent — if saving fails, Kai does not tell the customer they are unsubscribed. He would rather retry than confirm something that did not happen. The full behavior is documented in STOP, START, and HELP keywords.

None of this is unique to KaiCalls as a set of rules. Every registered campaign is supposed to work this way. What is worth knowing is that on KaiCalls they are gates in the sending code, not guidance to the business owner.

What the dashboard shows you

Under Dashboard > Compliance > A2P Setup, a business on a KaiCalls number sees a status card confirming that texts are sent through KaiCalls' registered campaign and no additional setup is required.

If a number's enrollment is still pending, the dashboard's activation status reads "Live for calls. SMS follow-ups are limited until A2P registration completes." Calls work normally during that window — registration only affects texting — and the note clears once the number is on the campaign. If it does not clear within a business day, that is worth a message to support, because it means reconciliation has not caught it either.

You can also confirm delivery yourself in about a minute: call your number from your cell, hang up before Kai answers, and watch for the missed-call text. Then open Dashboard > Messages and check that it shows as delivered. The step-by-step is in the A2P help page.

If you bring your own Twilio account

Some businesses connect their own Twilio account so their numbers live in an account they control. That changes who has to register: the numbers are yours, so the carriers need your brand and your campaign. KaiCalls' campaign does not cover numbers in someone else's account, and KaiCalls cannot file a brand or campaign on your behalf inside your Twilio account.

For those businesses, the A2P Setup page switches to a tracker. It lists what to gather — legal business name, EIN, address, authorized contact, use case, sample messages, keyword replies, and a consent description — shows your current status, and links directly to the Twilio console where you file. Brand review commonly takes one to two business days; campaign review three to five more.

The campaign filing is where most people get rejected, usually for a fixable wording problem. We wrote up what we learned in How to Write an A2P 10DLC Campaign That Gets Approved. Choose Customer Care as the type if the texts are replies and follow-ups, and make sure every number you want Kai to text from is attached to the messaging service tied to that campaign — a number outside it is unregistered even if the campaign is approved.

What KaiCalls does not do

Being precise about the edges is the point of this post.

Registration does not make every text deliver. It makes carriers trust the sender. Content that looks like spam can still be filtered from a registered number, which is why the content screen exists.
KaiCalls does not run toll-free verification. Toll-free numbers use a separate process from 10DLC. Ask support before choosing a toll-free number you plan to text from.
KaiCalls does not file brands or campaigns in your Twilio account. It tracks status and tells you what to gather. The filing is yours.
You cannot customize the keyword list or the STOP/HELP reply text per business today. They are the same on every KaiCalls number, which is also what keeps them consistent with what was registered.
None of this is legal advice. Registration and consent tooling reduce the chance of a mistake and keep a record. Deciding who your business should be contacting is still your call. See How KaiCalls Handles TCPA, Do Not Call, and A2P Compliance for where that line sits.

FAQ

Do I have to fill out A2P 10DLC forms to text with KaiCalls?
Not if you use a KaiCalls phone number. Your number is added to KaiCalls' registered Customer Care campaign when it is provisioned. Only businesses that connect their own Twilio account register their own brand and campaign.

What happens if adding my number to the campaign fails?
The number is held and not activated. The dashboard shows that texts are limited until registration completes, and the nightly reconciliation retries. If it does not clear within a business day, contact support.

Can I send marketing texts through KaiCalls?
No. The campaign is Customer Care. Kai screens outbound texts for marketing language, link shorteners, and excessive caps and blocks them before they leave. That protects your registration and everyone else's on the campaign.

Will customers see my number or a KaiCalls number?
Your number, whenever it is active and enrolled — which is the normal state. Only while enrollment is pending are texts routed through a KaiCalls sender so they still arrive.

What if I bring my own Twilio account?
Your numbers sit in your account, so the carriers need your brand and campaign. You register in the Twilio console; the A2P Setup page tracks your status and what to gather.

See it for yourself. Call the KaiCalls demo line at (417) 386-2898, hang up before Kai answers, and watch the follow-up text arrive from a registered number. Or visit kaicalls.com.

Why Your Business Texts Aren't Delivering: A 10DLC Troubleshooting Guide

connor gallic — Tue, 15 Sep 2026 15:02:40 +0000

When a business text shows as sent but the customer never gets it, the cause is almost always one of six things, and they are worth checking in order: the number is not registered for A2P 10DLC, the carrier filtered the message, the number hit a daily cap, the content looked like spam, the customer opted out, or the text was held for quiet hours. The first two account for the large majority of "my texts aren't working" reports, and both are invisible from the sending side unless you know where to look.

The frustrating thing about text delivery problems is that there is no bounce. An email that fails comes back. A call that fails gives you a busy signal. A filtered text just disappears, and the person who was supposed to receive it assumes you did not bother. For a business that depends on texting callers back, that is a customer lost without a trace.

This guide is written for a business owner, not a telecom engineer. Each cause has a symptom, a way to confirm it, and a fix. Where KaiCalls handles the fix for you, it says so.

Start here: read the delivery error
Cause 1: The number is not registered
Cause 2: The carrier filtered the message
Cause 3: The number hit a daily cap
Cause 4: The content looked like spam
Cause 5: The customer opted out
Cause 6: Quiet hours
A five-minute end-to-end test
FAQ

Start here: read the delivery error

Before guessing, look at what the sending platform recorded. On KaiCalls, open Dashboard > Messages, find the text, and read its status and any error on it. Most platforms built on the major messaging providers surface a numeric error code. The ones that matter here:

Code	What it means	Which cause below
30034	Sent from a 10DLC number not attached to an approved campaign	Cause 1
30024	Number is not provisioned for messaging	Cause 1
30023	Daily message cap for the number or campaign exceeded	Cause 3
30007	Carrier filtered the message as spam or a violation	Cause 2 or 4
30005 / 30006	Destination unknown or is a landline that cannot receive texts	Not a registration problem
Delivered, but the customer says no	Silent filtering or an opt-out	Cause 2, 5, or 6

If there is no error and the message says delivered, do not stop. Carriers sometimes accept and then drop, and the sender never hears about it. Keep going through the list.

Cause 1: The number is not registered

Symptom: Nothing from this number ever arrives, on any carrier, to anyone. Error 30034 or 30024 if the platform reports it.

Why: Since 2023, the major U.S. carriers block or heavily filter business texts from local numbers that are not attached to an approved A2P 10DLC campaign. Registration is per number — a business can have an approved campaign and still have an unregistered number if that number was never attached to it. The full explanation is in A2P 10DLC Explained.

Confirm it: On KaiCalls, open Dashboard > Compliance > A2P Setup. A business on a KaiCalls number should see "SMS Enabled via KaiCalls." If your activation status says "Live for calls. SMS follow-ups are limited until A2P registration completes," the number is still being enrolled.

Fix:

KaiCalls number: KaiCalls adds your number to its registered campaign when it is provisioned and re-checks every night. A pending status normally clears on its own. If it lasts more than one business day, contact support. In the meantime, texts are not dropped — they route through a registered KaiCalls sender until your number is enrolled. Details in How KaiCalls Handles A2P 10DLC Registration.
Your own Twilio account: You have to register a brand and campaign in the Twilio console, then attach each number to the messaging service tied to the campaign. An approved campaign with an unattached number still fails. See How to Write an A2P 10DLC Campaign That Gets Approved.

Cause 2: The carrier filtered the message

Symptom: Some texts arrive and some do not. One carrier's customers (say, everyone on T-Mobile) never get them while others do. Error 30007 if reported, but often nothing.

Why: Carriers run spam filters on registered traffic too. Registration tells them who you are; it does not exempt your messages from inspection. Filtering is triggered by content patterns (Cause 4), by sending too many near-identical messages in a short window, by a sudden volume spike from a number that was quiet, or by complaints from recipients who never opted in.

Confirm it: Send the same message to a few numbers on different carriers. Filtering is usually carrier-specific. Check whether the affected messages share a pattern: a link, a phrase, a time of day.

Fix: Address the content (Cause 4) and the consent (Cause 5). If you have your own campaign and filtering persists on clean, consented, low-volume traffic, your provider can open a ticket with the carrier; that is not something a business owner can do directly. On KaiCalls, Kai's content screen prevents the most common filtering triggers before a message leaves, so persistent filtering on a KaiCalls number is rare and worth a support message.

Cause 3: The number hit a daily cap

Symptom: Texts deliver fine in the morning, then stop late in the day. Error 30023 if reported. Resumes the next day.

Why: Every 10DLC campaign has a daily message cap on some carriers, set by the brand's trust score. Low-volume and sole-proprietor brands have small caps. Once the cap is exhausted, further messages that day are rejected.

Confirm it: Look at the time of the failures. Caps produce a clean cliff: everything before a certain hour worked, nothing after.

Fix: For a business on its own campaign, the options are to raise the brand's trust score through vetting or to spread traffic across the day. For a business texting callers back one at a time, caps are rarely the problem — they bite on blasts. If you are hitting a cap with conversational follow-ups, you are sending more than a Customer Care campaign expects, and that itself is a risk to the registration.

Cause 4: The content looked like spam

Symptom: Specific messages fail while others from the same number deliver. Often the failing ones contain a link.

Why: Filters key on patterns that spammers use: shortened URLs (bit.ly and similar), text that is mostly capital letters, dollar signs and "free" and "act now," very long messages, or a link with no context. A Customer Care campaign that starts sending promotional-looking text is also at risk of being reclassified.

Confirm it: Compare a failing message to a delivered one. Strip the link or the caps and resend to your own phone.

Fix: Use full, branded links rather than shorteners. Write like a person: sentence case, one idea, no sales language. Keep it short. On KaiCalls, Kai blocks messages with URL shorteners, over 1,600 characters, more than about 30% capitals, or marketing phrasing before they are sent — so if a message is blocked on your side, that is the content screen doing its job, and the fix is to reword.

Cause 5: The customer opted out

Symptom: One specific person never gets texts. Everyone else does. There may be a STOP somewhere in their thread.

Why: Once someone replies STOP (or UNSUBSCRIBE, CANCEL, END, QUIT, or "take me off your list"), every registered campaign is required to stop texting them. Only the customer can reverse it, by replying START. This is not a bug; it is the promise the registration is built on.

Confirm it: On KaiCalls, open Dashboard > Compliance > Consent and search the number. An opted-out number is labeled. Or scroll the thread in Messages for a STOP.

Fix: Do not try to work around it. If the customer actually wants texts, ask them to text START to your number. If they also asked you to stop calling, add them to your Do Not Call list. See STOP, START, and HELP keywords.

Cause 6: Quiet hours

Symptom: A text sent at 10 PM arrives at 8 the next morning. Or a text from a late-night missed call seems to be "missing" until morning.

Why: Texting a consumer late at night is both a compliance problem and a good way to earn a spam complaint. Well-behaved platforms hold texts during overnight hours in the recipient's time zone.

Confirm it: Check the timestamp on the missed call against the timestamp on the text.

Fix: Nothing to fix. On KaiCalls, texts between 9 PM and 8 AM recipient-local time are queued and sent in the morning, not dropped. If you would rather a late-night caller got nothing than a morning text, that is a setting worth discussing with support, but the default is the safer one.

A five-minute end-to-end test

Run this once when you set up, and again any time a customer reports a missing text.

From your own cell, call your business number and hang up before Kai answers.
Wait for the missed-call text. Note whether it arrives and how long it takes.
Open Dashboard > Messages. Find the text. Confirm it shows delivered with no error.
Reply STOP from your cell. Confirm you get the unsubscribe confirmation within a few seconds.
Open Dashboard > Compliance > Consent. Confirm your cell shows as opted out.
Reply START. Call and hang up again. Confirm the missed-call text comes back.

If step 2 fails, work Cause 1. If step 2 works for you but a customer reports otherwise, work Causes 2, 4, and 5 for that customer. If step 4 or 5 fails, contact support immediately — the opt-out loop is the one part of this that must never be broken.

FAQ

What does SMS error 30034 mean?
The message was sent from a US 10DLC number that is not attached to an approved A2P campaign. The fix is registration: attach the number to an approved campaign. On a KaiCalls number this is handled for you and normally clears within a day.

Why does my text say delivered but the customer never got it?
Some carriers accept a message and filter it afterward without reporting a failure. This is most common with unregistered numbers and spam-looking content. Check registration first, then content, then whether the person opted out.

Can a registered number still have texts blocked?
Yes. Registration earns trust; it does not exempt messages from filtering. Shorteners, caps, marketing language, and texting someone who replied STOP will all still fail.

Does texting from a toll-free number avoid all this?
No. Toll-free numbers have their own verification process instead of 10DLC, and unverified toll-free traffic is filtered too. KaiCalls does not run toll-free verification today.

My texts worked last month and stopped this week. What changed?
Most likely one of: the number fell out of its campaign (on KaiCalls, nightly reconciliation re-adds it), a message template changed to include a link or caps, or the customer opted out. Read the error on the failing message first.

Want texts that are registered before the first missed call? Sign up at kaicalls.com, or call the KaiCalls demo line at (417) 386-2898 and see the follow-up text arrive.

DEV Community: connor gallic

10DLC for Hair Salons, Hairdressers, and Barbers: What You Need to Text Clients

Table of Contents

Which salon texts need 10DLC

Reminders vs. promotions

Booth renters and solo stylists with no EIN

What you need before you start

Sample salon texts that pass review

How clients agree to get texts

Why salon texts get filtered

How KaiCalls handles it

FAQ

Your Phone System Is Your Growth Ceiling — Here's How to Remove It

Why Call Capacity Becomes a Growth Constraint

Where Humans Matter in the Call Flow

Call Records Create Operational Visibility

Why Voice Automation Is More Useful Now

What Changes When Routine Calls Stop Consuming the Team

A Safe First Week

AI Call Answering Cost Comparison for Law Firms: 2025 Guide

The Options

1. In-House Receptionist

2. Traditional Answering Services

3. AI Call Answering

Detailed Cost Comparison

Low Volume: 100 Minutes/Month

Medium Volume: 500 Minutes/Month

High Volume: 2,000 Minutes/Month

Hidden Costs to Consider

1. Billing Increments

2. Spam and Robocalls

3. Add-On Fees

4. Setup and Cancellation

5. After-Hours Premiums

ROI Calculator

Input Your Numbers:

Sample ROI Calculation

Making the Decision

Choose In-House When:

Choose Traditional Services When:

Choose AI When:

The Verdict

Ruby Receptionist Alternatives: 5 Options Compared (2026)

Which Ruby alternative should you shortlist?

Decide what you need the replacement to do

Five alternatives, with their practical trade-offs

1. KaiCalls: keep your team first and add a secretary

2. Smith.ai: live answering with work around the call

3. Goodcall: compare cost by different callers

4. Abby: a dedicated team with human and AI options

5. Moneypenny: human answering under the former VoiceNation brand

Compare the bill using your own call mix

Run this test before forwarding customer calls

Record what happened, not just whether the call sounded good

Move the call flow only after the handoff is clear

Questions to settle before switching from Ruby

Does Ruby offer 24/7 service?

Is an AI secretary a replacement for a human receptionist?

Can my team keep taking calls?

What is the cheapest Ruby alternative?

Try your call flow before you switch

Bilingual Legal Answering Service: 7 Options Compared

Which bilingual answering service fits your firm?

Overflow Call Answering Explained: Your Phone Rings First, Kai Takes the Rest

Table of Contents

What Is Overflow Call Answering?

When Do You Need Overflow Answering?

How Does Overflow Answering Work With KaiCalls?

Overflow vs. Forwarding Every Call

How Do You Set It Up?

FAQ

What is the difference between overflow and an answering service?

How long does my phone ring before Kai answers?

Can more than one phone ring first?

What happens to after-hours calls?

Will callers know it's a backup?

Do I need to change my number?

Help Desk Integration for Phone Calls: Turn Support Calls into Zendesk and ServiceNow Tickets

Table of Contents

Why Support Calls Belong in the Help Desk