Every conversation, with a clear next step.

Connection workspaces cover Sarvam AI, Exotel, Twilio, ElevenLabs and Vapi, with provider resource and webhook-event review.

Choose the supported language, web or telephone channel for your use case. Provider capabilities differ; the providers are not interchangeable.

Live use requires verified credentials, a supported adapter, organisation access and the relevant release checks. A saved connection alone does not enable calls.

Save assistant instructions, language and provider settings in the setup workspace.

Prepare the operating-hours and human callback approach, with an emergency stop available to administrators.

Available model and voice controls depend on the selected provider. Public sessions still require a reviewed release and pilot approval.

Prepare visitor-safe answers about projects, unit configurations, floor plans, brochures and RERA information from your reviewed material.

Manage source labels, versions, review dates, language and citation references before publishing answers.

Current retrieval matches reviewed FAQ text. Automatic brochure extraction and vector search are not verified parts of this workflow.

Review readiness checks and the formal release-approval workflow before publishing.

Keep configuration revisions and published-release history available for review.

Restore an earlier release into a draft while unpublished, then review and pass the normal publish checks again. Restoration does not instantly replace a live release.

Review recent calls, session outcomes, action records and attention flags.

Use transcript, citation and recording review only where the released channel, access and retention policies support them.

Live media, audio playback and automatic updates depend on the enabled provider runtime. Sample audio or a call record is not proof of a live stream.

Preview dormant leads and choose a campaign title, language, offer and conversation context.

Create campaign batches and queued call activities linked to the lead for review.

The reviewed campaign service records queued work. Automatic dialing, high-volume concurrency and outcome synchronisation require a separately verified live integration.

Preview the lead audience and prepare project location, unit types, starting price, possession information and launch offers.

Record the approved pitch and queued campaign activities in CRM.

Mass calling and automatic site-visit capture from this campaign are planned integrations. The current queue does not establish a completed outbound call.

Review the AMC renewal audience and prepare contract, warranty or service context for a campaign.

Keep the renewal offer and queued call activity with the relevant CRM record.

Predictive renewal scoring, automatic live calling and payment collection are outside the verified campaign scope. Confirm the follow-up and payment process separately.

Configure the inbound-lead response policy, delay, calling hours and available protection checks.

Review queued callback activities and use the workspace test trigger to inspect the simulated response.

A guaranteed 15–60 second live callback is not established by the current test or queue. Actual dialing and timing need a verified production integration.

Configure retry intervals, maximum attempts, calling hours and a WhatsApp fallback step.

Review the retry queue, attempt counts and escalation records.

Current actions update queue records. Live redial, provisioned caller-number rotation and WhatsApp dispatch from this queue are planned integrations; changing a status does not send a message or prevent spam flags.

Configure a telephone or SIP destination, escalation keywords, timeout, fallback and briefing prompt.

Simulate a handover and review the resulting transfer log and CRM activity.

Live warm transfer and private audio briefings require a supported released telephony path. A simulated transfer log does not confirm that a customer was connected.

Use the supervisor workspace to review session records and monitoring, whisper or takeover events.

Keep coaching annotations and intervention history connected to CRM context.

Current supervisor actions record state and notes. Live silent listening, private audio coaching and three-way barge-in need media integration and are not verified by those records.

Maintain battlecards for objections such as pricing, possession dates, competitors and finance questions.

Match supplied customer text against configured keywords, then record suggestion feedback.

Continuous in-call listening and a sub-150ms response are not verified. Your team reviews the suggested answer before using it.

Create, reschedule and track site-visit bookings with the project, map link, visit time and assigned salesperson.

Record the supported CRM meeting activity, export an ICS calendar invitation and use the configured WhatsApp pass workflow.

Confirm message delivery and calendar acceptance separately. External calendar slot locking and automatic conflict-free scheduling are planned integrations.

Configure supported follow-up templates and business context for project information, site visits or renewal reminders.

Use the supported send workflow and review follow-up history with your WhatsApp Business sender, consent and plan limits.

Automatic sending on every hangup, arbitrary PDF or VIP-pass generation and payment-link creation are not guaranteed by this setup. Confirm the enabled event triggers and template content.

Review campaign and call-activity views for outcomes, durations and follow-up context.

Explore the available cost and pipeline-attribution presentation with the team.

Some costs, revenue, pipeline figures and recording examples are estimated or sample values. These views are not verified carrier billing or audited ROI attribution.

Save persona profiles with regional accent, language, speaking speed, pitch and style preferences.

Prepare options such as Hinglish, Marathi-Hindi or Bengaluru English for provider review.

The current preview records settings and simulated synthesis information. Real audio generation, dialect fidelity and filler delivery depend on a verified provider integration.

Maintain trunk records, rate information, routing rules and recorded prepaid balance or usage.

Evaluate a preferred trunk and simulate a degraded connection or failover choice.

This workspace models routing decisions. Live Tata, Airtel, Exotel or Twilio switching, automatic top-ups and sub-second failover need separately verified carrier connections.

Maintain the organisation’s do-not-call records and configure daily caps and cooling-off periods.

Check eligible calling attempts against recorded restrictions and scan supplied transcripts for configured opt-out phrases.

A national DND registry connection is not verified. Confirm suppression coverage in each live calling path and your applicable consent requirements before rollout.

Evaluate supplied transcripts for configured disclosure or consent terms, prohibited phrases and talk-to-listen balance.

Review scores, checklist results, supervisor flags and coaching opportunities.

Current checks are rules and keyword based. They do not certify legal compliance, prove consent or guarantee automatic auditing of every call.

Create experiments, configure traffic allocation and associate call outcomes with a variant.

Compare results and confidence displays, choose a winner or enable the configured automatic promotion rule after its sample and performance thresholds.

Promotion updates the experiment and traffic split. Applying it to live conversations depends on the campaign integration; reliable conclusions require sufficient, correctly attributed production evidence.

Maintain terms, aliases and replacements for localities such as Hinjewadi or Kharadi and property terms such as 7/12 Satbara.

Test supplied transcript text and review corrections and word-level confidence visualisations.

This is text normalisation with calculated confidence displays. Acoustic-model fine-tuning, measured audio confidence and improved live speech recognition are planned provider work.

Prepare scenarios such as an NRI investor, a price negotiator, a first-time buyer or a customer asking to opt out.

Review generated sample dialogue and the sandbox’s script, objection and checklist score displays.

The current sandbox uses scripted dialogue and calculated scores. Live load testing, reliable hallucination detection and deployment certification are planned validation work.

Prepare DID number and trunk governance, routing policies, consent and recording controls.

Review supported outbound, handover, retention and reconciliation workspaces with the appropriate administrators.

Live inbound or outbound telephony depends on provider support, number provisioning, readiness evidence and deployment release gates.

Review provider health, circuit-breaker controls, service-level evidence and recorded incidents.

Keep recovery and resilience evidence with the voice operations review.

Evidence and targets are not an uptime guarantee. Confirm monitoring coverage and recovery behaviour for your released environment.

Review configuration revisions, release changes and available voice audit events.

Review transcript-access and governance evidence subject to the relevant permissions and retention policies.

Audit coverage depends on the event and released channel. Agree access, retention and review responsibilities for your organisation.

Review the CRM Voice subscription, plan controls, usage metering and available billing records.

Confirm included allowances, provider charges, overage rules and any commercial activation requirements.

A subscription does not enable every provider or telephone feature. Calling readiness and release approval remain separate checks.