Voice AI for masjids: a practical guide.

What a masjid voice agent actually does

The shorthand: it picks up the masjid phone, every time, in any language your community uses, with adab, and writes the outcome back to whatever system you already run on. The longer answer breaks into seven concrete jobs:

1. 01 · Inbound coverage

   Answers every call to your masjid line, 24/7, with proper salams. No more voicemail box that nobody checks for three days. No more missed Jummah questions because the only volunteer with the phone went to Madinah for Umrah.

2. 02 · Outbound campaigns

   Calls your members for Eid event RSVPs, fundraising follow-ups, iqamah-time changes, taraweeh schedule announcements. Consent-gated. Every uploaded number requires your members opted in to phone follow-up.

3. 03 · Routing + handoff

   When the caller wants a human (sensitive counseling, fiqh questions, a complaint about the khutbah), the agent transfers with the full transcript, language, and intent already in your imam's hands. No re-asking what the caller already said.

4. 04 · Knowledge base + RAG

   Reads your masjid website, prayer schedule, event calendar, and FAQ. Updates when you update them. The agent doesn't guess about Sunday Islamic school start times. It knows because your website knows.

5. 05 · CRM + donor logging

   Every donation pledge, every event RSVP, every counseling request gets a structured record in your CRM (MOHID, MasjidConnect, MasjidConnects, Masjidaa, or a Google Sheet, all of them work).

6. 06 · Multilingual

   English, Arabic (MSA + Gulf), and Urdu at launch. Indonesian, Malay, Turkish on the public roadmap. Bengali and Somali after that. Code-switching mid-call between English and the caller's tongue is the default, not a setting. See the full multilingual roadmap →

7. 07 · Halal-only refusal

   The platform itself refuses to onboard riba banks, alcohol, gambling, and conventional insurers. Your masjid runs on infrastructure that already drew the line. See the public refusal list →

The five call types that matter most

Every masjid we've studied (small ones in suburban Texas, mid-sized ones in East London, large ones in Toronto's GTA) surfaces the same five call types as the bottleneck. If your voice agent handles these, you've recovered most of the bandwidth your volunteers are losing.

1. The Jummah-time confirmation

Friday morning, the phone melts. “What time is khutbah this week?” “Is overflow parking open?” “Sisters' entrance still on the side?” Pre-iqamah, this is the highest-frequency call type any masjid receives, and the one where the “iqamah amanah” (the trust your masjid keeps with the congregation by holding the announced time) lives or dies. A voice agent handles every one of these in parallel, in the caller's language, without holding up your office.

2. The 3 AM Fajr-time question

A revert calls before Fajr asking how to make wudu. A new Muslim is in their first week and doesn't know what to do about a missed prayer. A community member is dealing with grief at 2 AM and reaches for the masjid phone first. None of these calls can wait until office hours, and none of them should be answered by a generic chatbot improvising a fiqh ruling. Akhi greets with adab, walks them through the basics it knows, and queues an imam callback at sunrise. Every deferral logged for the imam's records.

3. The Eid event RSVP

A family of seven calls to register for Eid prayer at the convention center your masjid books each year. The agent captures the names, the ages of the kids (for the children's program seating block), the accommodation needs (a wheelchair slot for grandfather, allergy-aware breakfast for the niece), and writes the structured record into your event CRM. Your volunteers stop being a phone bank that breaks down a week before Eid.

4. The donation pledge during Ramadan

Last 10 nights. The phone keeps ringing. Donors want to make their Zakat pledge before Laylatul Qadr passes them. The agent confirms the project eligibility against your imam's posted fatwa (“Yes, the orphan-sponsorship project qualifies for Zakat per Imam Abdullah”), captures the amount, arranges Zelle, ACH, or check pickup according to what the donor prefers, and emails the receipt before the call ends.

5. The revert + new-Muslim onboarding sequence

First call. First Jummah. First Ramadan. Your masjid's community presence in the life of a brand-new Muslim is the single most important thing you do, and most masjids don't have a structured intake because nobody owns it. Akhi greets the new Muslim with warmth, schedules them with your imam for shahadah confirmation, signs them up for the new Muslim halaqah, and texts them the address of the Saturday class with parking notes. Then logs every step into your members CRM so your imam can follow up next week.

What generic voice AI gets wrong

We're not arguing that horizontal voice AI is bad. Vapi, Retell, ElevenLabs, Bolna and the rest are technically excellent platforms. We're arguing that none of them are built for the masjid use case. The failure modes are predictable and recurring:

• Wrong pronunciation. Generic voice AI mispronounces wudu, salah, taraweeh, Jummah, Sayyiduna. The first 30 seconds of the call IS the credibility test, and your members hear when it fails.
• Wrong dialect. A Lebanese aunty calling in Levantine Arabic doesn't want a textbook MSA agent that sounds like a news anchor. A Pakistani uncle wants Urdu code-switched with English the way he actually talks.
• Wrong refusal posture. Generic agents will happily field a fiqh question and improvise an answer. That's a brand and a community catastrophe waiting to happen. Akhi defers. Every fiqh question goes to your imam.
• Wrong holidays. Generic agents say “Happy Holidays” in Ramadan. They don't know Eid from Christmas. They schedule outbound campaigns during fasting hours. The Islamic calendar is in our platform, not a setting your team has to remember.
• Wrong client base. The horizontal voice AI vendor your masjid would be sharing infrastructure with also serves alcohol brands, riba banks, and gambling sites. We refuse all three at the platform level. Public list of refusals →

Setup checklist for the brother on the board

You don't need a developer. You don't need a fiqh degree. You need about an hour, your masjid website URL, and two board signatures. Here's the order:

1. Step 1 · 5 minutes

   Submit the early-access request. Founder reviews each one personally during the first 30 customers. No form bot.

2. Step 2 · 15 minutes (you, on the call with us)

   Walk through your masjid's call patterns. Which questions hit the line most. Which volunteers cover which slots. What your iqamah times are. What your fiqh-handoff policy is for the imam.

3. Step 3 · 10 minutes

   Point Akhi at your masjid website. We auto-extract hours, prayer schedule, event calendar, FAQ. Anything missing, you upload as PDFs or paste into the dashboard.

4. Step 4 · 15 minutes

   Choose your telephony rail. Twilio, Plivo, or your existing SIP provider. We forward your masjid line, route after-hours to Akhi, and let your office staff cover business hours themselves if they prefer.

5. Step 5 · 10 minutes

   Adab review. We play you sample calls in your masjid's voice (English + Arabic + Urdu if relevant). You sign off or request adjustments. Standard turnaround for revisions is 24 hours.

6. Step 6 · go live

   Akhi answers calls. Outbound campaigns activate when you run them. The board gets a weekly summary of call volume, disposition, and follow-up actions captured.

What it costs

Pricing is per voice-minute, not per seat. That matters because most masjid budgets are voted annually and it's much easier to defend “we estimate 4,000 minutes a month at X cents per minute” than “we're paying for three seats whether or not we use them.” See the pricing page for current minute rates and the founder pricing tier for the first 30 customers →

For most small-to-mid masjids (200 to 800 musallis), the per-month cost lands somewhere between a couple of dinners and a part-time office stipend. The point is not to be the cheapest line item on your budget. It's to free your volunteer time for the work only humans can do.

Adab review: the gate that doesn't move

Before any language ships into a live agent, native speakers review the agent's transcripts on four checks: Islamic vocabulary correctness, refusal-policy enforcement in-language, halal-business filter intent recognition by dialect, and sensitive-topic handoff phrasing. Same gate for English. Same gate for Levantine Arabic. Same gate for Urdu. We agree with Al-Azhar and Egypt's Dar al-Ifta. AI is for ops, not for deen. Adab review is how we enforce that across every call your masjid ships through us. See the full adab review process →

Frequently asked