How to Set Up a Cloud IVR in 30 Minutes (2026)

If you've been quoted six weeks for an IVR setup, somebody is selling you the wrong product. Modern cloud IVR — like the one in Kedeyo's platform — goes live in 30 minutes. Here's the exact path from blank workspace to live menu, plus the testing checklist that prevents Day-1 disasters.

Before you start: 5 minutes of design thinking

Most failed IVRs fail because nobody thought about the routing first. Spend 5 minutes answering these:

1. Who answers calls today? — sales, support, billing? List the agent groups.
2. What % of calls go where? — rough distribution helps you design defaults
3. What's your busiest hour? — overflow routing for that hour
4. What's your after-hours behaviour? — voicemail, callback, route to night shift
5. Which calls should bypass the IVR? — VIP customers, known numbers

Step 1 — Get a virtual number (5 min)

Pick a city code that matches where your customers are. Mumbai 022, Delhi 011, Bengaluru 080. If you serve all India, pick a number based on your HQ. Provisioning is instant on most cloud platforms; cloud IVR pricing benchmarks for context.

Step 2 — Record (or generate) the greeting (5 min)

AI text-to-speech is good enough in 2026 for almost any business. Keep the greeting under 8 seconds. Format:

"नमस्ते. [Brand] में आपका स्वागत है। For English, press 9."

Two principles: lead in the language most customers speak; offer English as a secondary option.

Step 3 — Build the menu tree (10 min)

Drag-and-drop a 2-3 level tree. Rules of thumb:

• Max 5 options per level — humans can't hold more
• Most-common option first ("For order tracking, press 1")
• Skip-the-menu option — "To talk to an agent, press 0 anytime"
• No more than 3 levels deep — past that, callers hang up

Example structure for an e-commerce business:

1. Press 1 for order status → routes to OrderBot or order team
2. Press 2 for return / refund → routes to returns team
3. Press 3 for product enquiry → routes to sales team
4. Press 4 to speak to an agent → general queue
5. Press 0 anytime — agent override

Step 4 — Wire the routing (5 min)

Each menu option points to an agent group, a self-service flow or a follow-up menu. Configure:

• Working hours per group (9-7? 24/7?)
• After-hours behaviour — voicemail, AI Receptionist, or callback
• Overflow rules — when group is full, route where?
• VIP override — known phone numbers skip menu, route directly

Step 5 — Test with 5 real people (5 min)

Don't skip this. Have 5 colleagues call in cold and try a real task. You'll discover:

• Greeting too long — they hang up before menu starts
• Option labels confusing — people guess wrong
• Hindi pronunciation off — TTS sometimes gets words wrong
• Hold music too loud or absent
• After-hours fallback unclear

Day-1 monitoring

First 48 hours, watch the metrics dashboard. The two numbers that matter:

• Drop rate per menu level — if more than 30% drop at level 1, your greeting is too long
• 0-key escape rate — if more than 50% press 0 to skip the menu, your menu options aren't matching real intents

Bottom line

30 minutes from sign-up to live IVR is realistic in 2026 with the right platform. The menu design takes 10 of those minutes; the rest is configuration. Always test with 5 real callers before announcing the new number. Reference: TRAI for telecom rules that govern Indian commercial calling.