1(globalThis.TURBOPACK||(globalThis.TURBOPACK=[])).push(["object"==typeof document?document.currentScript:void 0,82628,e=>{"use strict";e.s(["CHANNEL_TO_URL",0,{sms:"/sms",whatsapp:"/whatsapp",rcs:"/rcs",voice:"/voice"},"INDUSTRIES",0,[{slug:"banking-finance",name:"Banking & Financial Services",shortName:"Banking & Finance",icon:"bi-bank",color:"#1B48E0",eyebrow:"Banking & BFSI Communication",headline:"SMS & WhatsApp Business API for Banks, NBFCs & Fintechs in India",subtitle:"OTP delivery, transaction alerts, EMI reminders, loan updates and KYC nudges â sent across SMS, WhatsApp, RCS and Voice with 99.9% uptime and TRAI DLT compliance.",intro:"Indian banking and financial services run on speed and trust. An OTP that does not land in three seconds breaks a payment journey. A transaction alert that arrives an hour late breaks fraud-prevention. A renewal reminder that misses a customer breaks retention. Ojiva AI gives banks, NBFCs, fintech apps, lending platforms, payment gateways and wealth managers a single multi-channel layer for every transactional, servicing and engagement touchpoint â designed from day one for TRAI DLT, RBI customer-communication expectations and the realities of the Indian telecom network. Whether your team handles a few thousand OTPs a day or millions of statements at month-end, the same APIs, dashboards and template controls scale with you, with sender-ID-level audit trails and consent enforcement baked in.",painPoints:[{title:"High-volume transactional traffic that cannot fail",body:"OTPs, debit alerts, statement notifications and KYC nudges run continuously across the day. Each one needs to land in seconds, on every operator, with predictable cost. A single failed OTP can break a checkout, while a delayed fraud alert can mean a customer loses money â both translate directly to support tickets, lost revenue and regulator scrutiny."},{title:"Strict regulatory boundaries with zero margin for error",body:"TRAI DLT registration, RBI guidance on customer communication, KYC consent rules and template approval across every bank-customer touchpoint leave no room for ad-hoc messaging. Sender IDs, content templates, opt-outs and audit logs need to be ready the moment a regulator asks. Compliance failures here are not a slap on the wrist â they are blocking issues for your messaging programme."},{title:"Brand trust is built and broken in the inbox",body:"A bounced OTP, a fraud-warning sent late, a generic-looking promotional template that gets reported as spam â every one chips away at customer confidence. For regulated brands, the messaging stack is not infrastru
1cture plumbing; it is part of the brand experience. Customers form an opinion of the bank in those few-second interactions every single day."}],channelFit:[{channel:"sms",label:"Bulk SMS",use:"OTP, transaction alerts & account notifications â DLT compliant Bulk SMS",body:"The default rail for transactional banking traffic. DLT-registered sender IDs, pre-approved templates and direct telecom routing keep delivery fast and consistent across Jio, Airtel, Vi and BSNL. Used for OTP at login, debit and credit alerts, EMI due notifications, monthly statement availability and KYC document requests."},{channel:"whatsapp",label:"WhatsApp API",use:"Loan updates, EMI collection & KYC nudges via WhatsApp Business API",body:"WhatsApp Business API handles richer customer-servicing flows where a two-way conversation makes sense â KYC document collection, branch appointment booking, basic account servicing, and bot-to-agent handoff for live support. Templates handle proactive outreach; sessions handle responsive servicing."},{channel:"rcs",label:"RCS Messaging",use:"Verified branded RCS messaging for premium banking communication",body:"RCS Business Messaging adds verified sender identity, brand colours and rich cards to messages on supported Android devices. Useful for monthly statement summaries, secure link delivery for net-banking flows, and any communication where trust signalling matters."},{channel:"voice",label:"Voice Call",use:"IVR for collections, OTP fallback & loan-due reminder calls",body:"Outbound voice handles the highest-stakes, highest-value contact moments â collection IVR for overdue loans, fraud-alert call-back flows, and customer-verification calls that need confirmation in the moment. Multi-language support helps cover Tier-2 and Tier-3 markets."}],useCases:[{title:"OTP for login, payments and KYC",body:"Multi-channel OTP delivery so customers never get stuck at checkout, login or KYC. Configure SMS as primary with WhatsApp / Voice fallback so a single channel hiccup does not block a transaction."},{title:"Transaction & fraud alerts",body:'Instant SMS or WhatsApp alerts for debits, credits, login attempts, card swipes and unusual activity. Templates can include amount, merchant, timestamp and a one-tap "Not me" link to a fraud-handling flow.'},{title:"EMI & collection reminders",body:"Automated reminder cadence ahead of due dates, on the due date, and through the grace period. Voice-call fallback handles the highest-value loans where direct contact converts better than messaging."},{title:"Monthly statements & re-KYC",body:"Send statement-ready alerts with secure portal links, schedule periodic re-KYC nudges, and trigger event-based document requests directly into customer WhatsApp threads with full template safety."},{title:"New product cross-sell",body:"Send compliant promotional offers to opted-in customers with segment-aware copy â pre-approved loan offers, credit-card upgrades, fixed-deposit renewals â separated cleanly from your transactional traffic."},{title:"Customer servicing on WhatsApp",body:'Run an "always-on" WhatsApp servicing channel where customers can check balances, raise complaints, schedule branch visits and reach a live agent without dialling a call-centre.'}],outcomes:[{label:"Faster transaction journeys",body:"Cut drop-offs at OTP and KYC steps by routing across the channel a customer is most likely to receive on first try."},{label:"Lower call-centre load",body:"Move routine servicing â balance checks, statement requests, branch booking â out of the IVR queue and into asynchronous WhatsApp."},{label:"Improved collection contact rates",body:"Use a multi-channel reminder cadence so every overdue customer is reachable somewhere â not just on a single number that may not be answered."},{label:"Cleaner regulator audit trail",body:"Per-template approval records, per-message delivery logs and per-customer consent state make audits a query, not a fire-drill."},{label:"Brand-consistent customer touch",body:"Verified senders, approved templates and brand-coloured RCS messages keep every customer-facing communication visibly on-brand."}],bestPractices:[{title:"Separate transactional and promotional sender IDs",body:"Keep one sender ID for OTP and account-related traffic, a different one for offers. This protects deliverability and respects DLT-template categorisation."},{title:"Build OTP fallback into the customer journey, not the message",body:"When SMS fails, the next channel should retry automatically â without the user having to ask for a new OTP. The handoff lives in your backend, not in copy."},{title:"Treat templates like product features",body:"Version-control templates, test changes in sandbox, and roll out per-segment. A template change is a customer-experience change."},{title:"Capture consent at the point of value",body:"Don't bury consent in a 30-page T&C. Capture it in the same screen where the customer chooses to receive a notification, with clear opt-out."},{title:"Send fraud alerts before the customer notices",body:"For unusual transactions, the message should arrive faster than a customer's heart rate spike. That requires direct connectivity, not bulk-aggregator queuing."}],implementation:[{title:"REST API + webhooks",body:"A single REST API handles outbound message creation across SMS, WhatsApp, RCS and Voice. Signed webhooks deliver delivery, read and click events directly into your core banking event bus."},{title:"Core-banking integration",body:"Trigger messages from any event in your core or LOS â transaction posted, OTP requested, EMI due â using the API or no-code workflow builder. Integrations are typically built by the bank's tech team in a few sprints."},{title:"Sandbox before production",body:"Per-environment API keys let teams test full flows in sandbox with isolated
1webhooks before promoting to production. Templates can be promoted between environments with version tracking."},{title:"Compliance-first onboarding",body:"Sender ID and template registration support is included as part of onboarding. The Ojiva team helps map your message catalogue onto DLT categories and templates so go-live is not blocked by registration backlogs."}],complianceNotes:"TRAI DLT-ready, supports sender ID and template registration, opt-in / opt-out enforcement, and audit logs that align with RBI customer-communication expectations.",complianceDetail:"Banking communication in India sits at the intersection of TRAI rules (DLT registration, sender ID rules, opt-out enforcement) and RBI expectations (customer consent, preserved records, secure handling of customer identifiers). Ojiva AI is built so both sets of obligations are operationalised â not added as an afterthought. Sender IDs and templates are registered on the DLT platform with the right principal entity and category; transactional and promotional traffic stays cleanly separated; opt-outs are honoured at the template and customer level; per-message logs are queryable for the period your audit team requires; and customer phone numbers and OTP codes are encrypted in transit and at rest, with OTPs stored as one-time-use hashes only.",faqs:[{q:"Is the platform DLT-registered for transactional and OTP traffic?",a:"Yes â sender IDs and templates are registered on the DLT platform with TRAI-aligned consent and opt-out workflows. Onboarding includes assistance with PE registration, header registration and template approval on your behalf."},{q:"Can I run multi-channel OTP fallback?",a:"Yes â configure SMS as the primary channel and WhatsApp or Voice as fallback, so OTP delivery succeeds even when one channel is degraded. Fallback is server-side, so the customer sees a single OTP request, not multiple."},{q:"Are templates pre-approved for banking use cases?",a:"A library of common transactional and OTP templates is available as a starting point; we assist with template approval for your specific copy, language variants and brand voice."},{q:"How do you handle sensitive data?",a:"Customer phone numbers and OTP codes are encrypted in transit (TLS 1.3) and at rest. OTPs are stored only as one-way hashes for verification, with automatic expiry and one-time-use enforcement. Detailed security documentation is available on request."},{q:"Can large institutions deploy in private environments?",a:"Yes â enterprise contracts can include dedicated infrastructure, private telecom routes, or single-tenant environments for institutions whose risk team requires data isolation. Contact sales to scope."},{q:"Will it integrate with our core banking system?",a:"Yes. A REST API and signed webhooks support integration with most core banking, LOS and CRM platforms used by Indian institutions. Specific connector readiness can be confirmed with our solutions team."},{q:"What happens during a telecom outage?",a:"Messages can route across multiple operator paths and channels. If SMS to a particular operator is degraded, fallback to WhatsApp or Voice keeps the OTP / alert flowing. Delivery state is reported per attempt for retry policies."},{q:"Can promotional and transactional messages share the same account?",a:"Yes â they share account-level controls but use separate sender IDs, separate template categories on DLT and separate opt-out lists, so promotional opt-outs do not stop transactional alerts."}]},{slug:"ecommerce-retail",name:"E-commerce & Retail",shortName:"E-commerce & Retail",icon:"bi-cart-fill",color:"#FF6D42",eyebrow:"E-commerce & D2C Solutions",headline:"WhatsApp & SMS Marketing for E-commerce & D2C Brands in India",subtitle:"Recover abandoned carts, confirm COD orders, send real-time shipping updates and win repeat purchases â with WhatsApp Business API, Bulk SMS and RCS for Indian online stores.",intro:"Indian e-commerce and D2C retail run on margins thin enough that every recovered cart, every successful COD delivery and every repeat order matters. The difference between a healthy CAC and an unsustainable one is often nothing more than messaging hygiene â does the cart-recovery WhatsApp land at the right moment, does the shipping update build delivery confidence, does the COD-confirmation call cut your RTO. Ojiva AI gives e-commerce, marketplace, D2C and quick-commerce teams a unified messaging layer across SMS, WhatsApp Business API, RCS and Voice that plugs into Shopify, WooCommerce, Magento and most popular Indian commerce stacks. Templates are pre-approved on DLT, transactional and promotional traffic stay separated, and per-customer segmentation handles the difference between a first-time buyer and a high-LTV repeat customer.",painPoints:[{title:"Cart abandonment that compounds across the day",body:"Most baskets are abandoned. The recovery window is short, the channel matters more than the discount, and the right nudge â at the right minute â recovers a meaningful share of revenue. A generic email an hour later does not."},{title:"Delivery & returns that decide repeat-purchase intent",body:'Customers form their opinion of an order in the gap between "ordered" and "delivered". Real-time visibility, clean handovers and frictionless returns are now table-stakes; lacking them, the next order goes to a competitor.'},{title:"Promotional fatigue that quietly kills your list",body:'Generic "FLAT 20% OFF" blasts get unsubscribed, reported, and silently filtered. Personalised, channel-appropriate, segment-aware messaging keeps engagement healthy and protects sender reputation across operators.'}],channelFit:[{channel:"sms",label:"Bulk SMS",use:"Order confirmation, COD alerts & shipping updates via Bulk SMS India",body:"The reliable rail for transactional commerce traffic â order placed, payment confirmed, shipped, out-for-delivery, delivered. DLT-registered templates keep deliverability healthy across operators."},{channel:"whatsapp",label:"WhatsApp API",use:"Cart recovery, order tracking & customer support on WhatsApp API",body:"WhatsApp is where Indian buyers actually live. Use it for cart recovery, two-way order support, catalogue browsing with product cards, and reorder flows for high-frequency products."},{channel:"rcs",label:"RCS Messaging",use:"Rich product carousels, promotional offers & verified sender via RCS",body:"Rich product carousels, branded sale offers, verified sender â RCS lets premium brands present their store experience inside the inbox on supported devices."},{channel:"voice",label:"Voice Call",use:"COD confirmation IVR, failed-delivery rescheduling & feedback calls",body:"Automated voice for COD-confirmation, delivery rescheduling and missed-OTP recovery. Particularly useful for high-AOV orders where a phone confirmation cuts RTO."}],useCases:[{title:"Abandoned cart recovery",body:"Trigger a WhatsApp or SMS nudge minutes after checkout drop-off, with a one-click return-to-cart link. A second nudge after a few hours, a third the next day, and stop â respect the customer."},{title:"Order & shipping lifecycle",body:'Automated transactional updates for "order placed", "payment confirmed", "out for delivery", "delivered", with carrier tracking links and a post-delivery NPS request.'},{title:"COD confirmation & RTO reduction",body:"Voice IVR or WhatsApp button-confirmation immediately after order placement to verify the buyer is real and ready to receive the package, dramatically reducing return-to-origin losses on high-value orders."},{title:"Loyalty & repeat sales",body:"WhatsApp catalogues, segment-based offers, and birthday / festive campaigns to drive repeat purchase from existing customers â usually a 5Ã cheaper acquisition path than paid media."},{title:"Reorder & subscription nudges",body:"For consumables or subscriptions, schedule a WhatsApp reorder nudge at the right interval per product. One tap to re-purchase keeps lifetime value compounding."},{title:"Review & UGC collection",body:"Day-after-delivery review nudge with a one-tap rating link. WhatsApp button collection of photos and short clips builds your social proof library passively."}],outcomes:[{label:"Higher recovered revenue from carts",body:"A multi-touch WhatsApp + SMS recovery flow recovers more carts than a single-channel email sequence â the channel is the lever."},{label:"Lower RTO on cash-on-delivery orders",body:'Pre-shipment confirmation flows cut "buyer not available" failures and protect margins on COD orders.'}
1,{label:"Reduced support inbound on order status",body:"Real-time shipping updates remove the most common support ticket type, freeing the team for higher-value conversations."},{label:"Higher repeat-purchase rates",body:"Segment-driven WhatsApp catalogues and reorder nudges keep customers engaged without burning the promotional list."},{label:"Cleaner sender reputation across operators",body:"DLT-aware template hygiene and per-segment audience targeting protect deliverability â no surprise blocks on Diwali day."}],bestPractices:[{title:"Recover carts with utility, not desperation",body:"The first nudge should help, not beg. Show what was left behind, not a panic discount. Save the discount for the second touchpoint."},{title:"Send shipping updates from a recognisable sender",body:"Customers should immediately know it is your brand. A registered DLT sender ID, a brand-coloured RCS card, or a verified WhatsApp Business profile all do this."},{title:"Throttle promotional volume per customer",body:"Even your best customers should not get more than 2-3 promotional touches per week. Past that, opt-outs and reports compound."},{title:"Confirm COD orders within minutes",body:"The longer you wait, the more the customer disengages. Aim for an automated voice or WhatsApp confirmation in the first hour."},{title:"Treat first-purchase moments as content",body:"Order placed, shipped, delivered, review request â these are five chances to build the relationship. Each message should add one piece of brand voice."}],implementation:[{title:"Connect to your store",body:"REST API + webhooks support most popular Indian and global commerce stacks. Order events from Shopify, WooCommerce, Magento, BigCommerce or your custom stack become triggers in the messaging layer."},{title:"Sync customer segments",body:"Push customer segments â first-time buyer, repeat buyer, lapsed buyer, high-LTV â into the platform via API or CSV. Use them as the audience for any campaign."},{title:"No-code recovery flows",body:"A 3-step cart-recovery flow can be built in the dashboard without code. More advanced multi-channel flows use the visual builder or REST API."},{title:"Sandbox + production",body:"Test order-confirmation, cart-recovery and COD flows in sandbox with test phone numbers before production rollout. Promote templates with version tracking."}],complianceNotes:"DLT-registered transactional flows, opt-out compliance, and message-template safety â so promotional and transactional traffic stay neatly separated.",complianceDetail:"E-commerce messaging is subject to the same TRAI DLT framework as banking â sender IDs, templates and opt-out enforcement matter just as much. Where commerce diverges is in the much higher promotional-to-transactional ratio: a typical store sends one transactional message per order but several promotional messages per active customer per week. Ojiva AI separates these flows cleanly: distinct DLT sender IDs, distinct template categories, separate opt-out lists for promotional vs. transactional, and per-customer frequency caps that prevent your active list from ever feeling spammed. Promotional opt-outs do not block transactional alerts (a customer who opted out of offers still gets shipping updates), and per-template audit logs let you respond to operator queries quickly.",faqs:[{q:"Can it integrate with my Shopify or WooCommerce store?",a:"Yes â webhook and REST API endpoints support most popular Indian and global e-commerce stacks. Orders, abandoned checkouts and customer events become triggers for messaging flows. Specific connector availability can be confirmed with sales."},{q:"How quickly can I run cart-recovery flows?",a:"A simple two-step recovery flow can be built in the dashboard without code in under a day. More advanced multi-step or multi-channel flows use the visual builder or REST API and typically take a sprint."},{q:"Do you support COD confirmation?",a:"Yes â voice IVR and WhatsApp button confirmation are both supported as ways to verify COD intent before pickup. Both can be wired into your OMS so unconfirmed orders are auto-cancelled or held."},{q:"Will my promotional messages stay within DLT rules?",a:"Promotional templates are registered separately from transactional ones, with opt-in / opt-out tracking enforced at the platform level. Templates that drift outside the registered category are flagged before send."},{q:"Can I segment by customer behaviour?",a:"Yes â segments can be built on order history, basket value, recency, channel preference and any custom attribute pushed via API. Segments are then targetable by any campaign or flow."},{q:"Can I run WhatsApp catalogues?",a:'Yes â WhatsApp Business API supports catalogue browsing inside the chat, with product cards, prices and "Add to Cart" buttons. Catalogue items can sync from your store.'},{q:"How are returns and refunds handled?",a:"Refund and return updates flow through the same transactional templates. WhatsApp interactive buttons let buyers initiate a return or pickup without contacting support."},{q:"What happens during festive-season volume spikes?",a:"Throughput is sized for transactional bursts. Enterprise plans add dedicated routes for predictable Diwali / EoSS / sale peaks so messages do not queue up in the busy hours."}]},{slug:"healthcare",name:"Healthcare",shortName:"Healthcare",icon:"bi-heart-pulse-fill",color:"#16a34a",eyebrow:"Healthcare Patient
1Communication",headline:"Patient Communication Platform for Hospitals in India",subtitle:'Reduce no-shows by 40%, automate "report ready" alerts, send medication reminders and run post-discharge follow-ups â all via SMS, WhatsApp Business API and Voice.',intro:'Indian healthcare runs on appointments, reports and follow-ups. Front-desk staff at hospitals and clinics spend hours every day on routine confirmation calls and "is the report ready" enquiries â work that automation can absorb completely. Ojiva AI gives multi-specialty hospitals, single-doctor clinics, dental and eye-care chains, diagnostic labs, IVF centres and home-healthcare providers a single platform for every patient-communication touchpoint. Appointment reminders go out over SMS and WhatsApp at the right interval, lab reports trigger a "ready" notification with a secure link the moment they\'re signed off, medication and refill nudges keep adherence high, and post-discharge or post-procedure follow-up flows close the loop on outcomes. Templates are designed with patient-data sensitivity in mind â patients are reminded what they need to know without exposing diagnostic detail over open channels.',painPoints:[{title:"No-shows and late arrivals waste clinical capacity",body:"A missed appointment is a clinician hour gone. Across a multi-specialty unit, daily no-show rates compound into measurable revenue loss and patient backlog. The right reminder, at the right time, on the right channel, dramatically reduces them."},{title:"Front-desk teams stuck on manual phone follow-ups",body:"Staff time spent confirming appointments, calling about lab readiness, or chasing follow-ups is staff time not spent helping patients in the building. This is exactly the work asynchronous messaging absorbs best."},{title:"Patient data and consent need careful handling",body:'Healthcare communication has to balance helpfulness with privacy. A reminder should mention "your report is ready" â not the diagnostic detail. A vaccination drive should target the right age band â not the wrong one. The templates need to be designed with this in mind.'}],channelFit:[{channel:"sms",label:"Bulk SMS",use:"Appointment reminders, OTP for portal login & lab-ready alerts via SMS",body:'Reliable rail for time-sensitive patient touchpoints â appointment confirmation, reschedule reminders, OTP for patient-portal login, "your report is ready" alerts. DLT-registered templates handle Indian operator nuances.'},{channel:"whatsapp",label:"WhatsApp API",use:"Two-way appointment booking, prescription pickup & patient follow-ups on WhatsApp",body:'Where richer patient interactions belong â interactive appointment confirmation buttons, prescription pickup notifications, post-procedure check-ins, and a chat-based "ask the front desk" flow that frees the phone line.'},{channel:"rcs",label:"RCS Messaging",use:"Branded hospital RCS messages with verified sender identity",body:"For supported devices, RCS adds the hospital brand, verified sender mark and rich cards. Useful for branded appointment reminders and secure document delivery where patients value the trust signal."},{channel:"voice",label:"Voice Call",use:"IVR appointment confirmation, vaccination drives & post-discharge wellness calls",body:"Automated voice for the patient cohorts that prefer it â older patients, vaccination camp invites, post-discharge wellness checks and missed-OTP recovery. Multi-language support helps clinics serving multiple linguistic communities."}],useCases:[{title:"Appointment reminders",body:"SMS or WhatsApp nudges 24 hours and 1 hour before, with a confirm / reschedule action. Reduce no-shows and let patients reschedule without calling the front desk."},{title:"Lab report ready alerts",body:'Notify patients the moment a report is signed off, with a secure link to view or download from your patient portal. Drop the "is my report ready" call volume to near-zero.'},{title:"Medication & refill nudges",body:"Scheduled reminders to take medication on a multi-day course, refill a prescription before it runs out, or book the next consultation. Especially useful for chronic-disease management."},{title:"Post-discharge & post-procedure follow-up",body:"Day-1, day-3 and day-7 wellness check-ins after a discharge or procedure. Pick up red-flag symptoms early and route patients back to the right clinician."},{title:"Vaccination & camp drives",body:"High-volume voice and SMS broadcasts for community drives, screening camps and public-health programmes. WhatsApp confirmation buttons let inv
1itees register their slot."},{title:"Patient feedback & NPS",body:"Day-after-visit feedback request via WhatsApp with a one-tap rating. Capture issues early, route compliments to the team, and build review volume on Google / Practo passively."}],outcomes:[{label:"Lower appointment no-show rates",body:"Multi-touch reminder cadences across SMS and WhatsApp meaningfully reduce missed appointments â and the front-desk burden of confirming them."},{label:'Reduced "is my report ready" call volume',body:"Auto-trigger of report-ready alerts removes one of the most common inbound queries to the front desk."},{label:"Better medication adherence",body:"Scheduled nudges for chronic-disease patients improve adherence, which directly improves clinical outcomes."},{label:"Higher review and NPS volume",body:"A single post-visit WhatsApp request collects feedback at scale â a new pipeline of organic reviews."},{label:"Front-desk hours freed up",body:"Routine confirmation, reschedule and report-ready calls disappear from the queue, letting staff focus on patients in the building."}],bestPractices:[{title:"Time reminders to your patient mix",body:"Younger patients need 1-hour reminders. Older patients need 24-hour reminders. Mixed clinics should send both. Test the mix per specialty."},{title:"Keep diagnostic detail off open channels",body:'A message can say "your report is ready" or "your appointment is at 3pm with Dr X" â but never share specific diagnostic findings or sensitive results in the message body.'},{title:"Use interactive buttons for confirmation",body:"WhatsApp interactive buttons for confirm / reschedule / cancel get higher response than asking the patient to call back."},{title:"Localise templates by language",body:"For multi-lingual catchments, send the same reminder in the patient's preferred language. Hindi, Tamil, Telugu, Kannada, Marathi, Bengali templates can all be approved."},{title:"Close the loop on red flags",body:'Post-discharge wellness check-ins should route any "not feeling well" answer immediately to a clinician, not into a generic support queue.'}],implementation:[{title:"HIS / EMR integration",body:"A REST API and webhooks let your hospital information system, EMR or appointment-booking platform trigger messages on the right events. Specific connector readiness can be confirmed with our team."},{title:"Multi-branch architecture",body:"Multi-branch hospital chains can have per-branch sender IDs, per-branch templates, and per-branch reporting under one parent account, with role-based access for branch admins."},{title:"Patient-portal OTP",body:"OTP for patient-portal login is a single API call. Multi-channel fallback (SMS â WhatsApp â Voice) keeps login success rates high even when one channel is degraded."},{title:"Template approval support",body:"Healthcare templates often need iteration through DLT and WhatsApp template approval. Onboarding includes assistance designing approval-ready templates that respect patient privacy."}],complianceNotes:"Patient identifiers and health context are handled with template-level safeguards. Templates can be designed to share status without exposing diagnostic details over open channels.",complianceDetail:'Healthcare communication needs to balance two things: helpful, timely information for the patient, and careful handling of any data that could identify them or their medical condition. Ojiva AI supports this by keeping diagnostic detail out of message bodies (a "report ready" alert points to a secure portal â it does not contain the report), enforcing template-level review before any content goes live, supporting per-patient consent and opt-out (so a patient can opt out of campaign messaging without losing access to clinical reminders), and providing per-message audit trails for the duration your compliance team requires. For institutions with stricter data-handling policies, enterprise contracts can include private deployments with data isolation.',faqs:[{q:"Can patients confirm or reschedule from the message itself?",a:"Yes â WhatsApp interactive buttons and RCS suggested replies let patients confirm, reschedule, or cancel without calling the clinic. The action triggers a webhook back to your HIS / appointment-booking system in real time."},{q:"How are reminders timed?",a:"Reminders can be scheduled relative to the appointment (e.g., 24 hours before, 1 hour before, on the day) and triggered automatically from your booking system via API or webhook. Different specialties can use different cadences."},{q:"Can it integrate with our hospital information system?",a:"Yes â a REST API and webhooks let your HIS / EMR trigger messages on appointment, report and discharge events. Specific connector readiness for the major Indian HIS platforms can be confirmed with our team."},{q:"Are patient OTPs handled securely?",a:"OTPs are encrypted in transit and at rest, stored only as one-way hashes for verification, and automatically expire. Multi-channel OTP fallback (SMS â WhatsApp â Voice) keeps patient-portal logins working even when one channel is degraded."},{q:"Is the platform suitable for chains with multiple branches?",a:"Yes â multi-branch setups can have per-branch sender IDs, templates and reporting under one parent account, with role-based access for branch admins and a consolidated view for HQ."},{q:"Can we send reminders in regional languages?",a:"Yes â Unicode SMS supports major Indian scripts. WhatsApp and RCS templates can be approved in Hindi, Tamil, Telugu, Kannada, Marathi, Bengali, Gujarati and other regional languages, sent based on patient-language preference."},{q:"How is patient feedback collected?",a:"A single WhatsApp message after the visit with a 1-5 rating button collects NPS at scale. Negative scores can be routed to your patient-relations team for follow-up; positive scores can be invited to leave a Google or Practo review."},{q:"Can it support vaccination or screening camp drives?",a:"Yes â bulk voice and SMS broadcasts can reach a wide cohort quickly, with WhatsApp confirmation buttons letting invitees register their slot. Useful for school health drives, community vaccination campaigns and corporate health camps."}]},{slug:"education",name:"Education & EdTech",shortName:"Education",icon:"bi-mortarboard-fill",color:"#7C3AED",eyebrow:"Education & EdTech Communication",headline:"WhatsApp & SMS for Schools, Colleges & EdTech in India",subtitle:"Send admission updates, automate fee reminders, share exam results and enable parentâteacher communication â via WhatsApp Business API and Bulk SMS for Indian education institutions.",intro:"Indian education runs on parent communication. Schools, colleges, coaching institutes, online edtech platforms and tuition centres have to keep parents and learners in the loop on admission, fees, attendance, exams, results and day-to-day school logistics. Email open rates from parents are notoriously low; WhatsApp and SMS are where messages actually get read. Ojiva AI gives education institutions a single platform for every parent / learner touchpoint â fee reminders, attendance alerts, exam results, admission counselling, parent-teacher meeting invitations and bus / transport notifications. Templates are DLT-registered, parental consent is captured at enrolment, and per-language support handles the linguistic diversity of Indian schools and colleges.",painPoints:[{title:"Reaching parents reliably with high-stakes updates",body:"Email gets ignored. Phone calls get screened. WhatsApp and SMS land. The channel mix has to match where parents actually engage, especially for time-sensitive updates like attendance alerts or unscheduled school closures."},{title:"High-volume admission cycles that need scale",body:"Admission season runs counselling, document collection, fee payment and slot allocation â all in the same few weeks. Manual call-centre follow-up doesn't scale; automated WhatsApp + SMS journeys do."},{title:"Fragmented systems across LMS, ERP, fee gateway",body:"A typical institute runs a school ERP, a learning platform, a fee-management gateway and an exam portal â each with its own notification preferences. A unified messaging layer that integrates with all of them is rare."}],channelFit:[{channel:"sms",label:"Bulk SMS",use:"Fee reminders, exam notifications & attendance alerts via Bulk SMS",body:"Workhorse for parent communication â fee due, fee received, attendance below threshold, exam date confirmation, result publication. DLT-registered templates land reliably across operators."},{channel:"whatsapp",label:"WhatsApp API",use:"Admission counselling, parent updates & fee collection on WhatsApp",body:"WhatsApp handles the richer flows â admission counselling, document collection, parent-teacher chat, study material delivery and result-portal links. Two-way conversation makes it the right channel for anything beyond a notification."},{channel:"rcs",label:"RCS Messaging",use:"Rich result cards, event invitations & branded school communication via RCS",body:"For enrolment campaigns and event invitations, RCS adds the institute brand, verified sender mark and rich card layout on supp
1orted Android devices â useful for premium / international school marketing."},{channel:"voice",label:"Voice Call",use:"Parent call campaigns, exam day reminders & result announcement IVR",body:"Automated voice broadcasts for unscheduled closures, weather alerts, parent-teacher meeting invites and bus-route changes. Reaches parents who don't engage with text channels."}],useCases:[{title:"Admission journey",body:"From enquiry to fee payment, automate the full applicant funnel â enquiry acknowledgement, counsellor follow-up, document collection, slot booking, fee receipt â using WhatsApp + SMS touchpoints."},{title:"Fee & attendance alerts",body:"Trigger SMS or WhatsApp the same day a fee instalment is due or a student is marked absent. Let parents pay or respond directly from the message."},{title:"Exam & result publishing",body:"Bulk-publish results to thousands of students and parents the moment they're ready, with a secure result-portal link. Handle dispatch in minutes, not days."},{title:"Parentâteacher engagement",body:"Two-way WhatsApp threads for class teachers, with safe templates and audit trail. Parents reach the right teacher; teachers reach the right parent group."},{title:"Bus / transport notifications",body:'Same-day "bus delayed by 15 minutes" or "route changed" notifications go out over SMS and voice â particularly important for younger students and concerned parents.'},{title:"Re-engagement of inactive learners",body:"For online edtech and coaching, a weekly nudge for learners who haven't logged in keeps engagement up. Course-completion celebration messages drive next-course enrolment."}],outcomes:[{label:"Faster fee collection cycles",body:"Multi-touch fee reminders across SMS and WhatsApp shorten the average time from due-date to payment."},{label:"Higher admission funnel conversion",body:"Automated counselling drips keep enquiries warm without burning counsellor capacity."},{label:"Reduced front-office call volume",body:"Routine queries â fee status, attendance, schedule, transport â move from phone calls to instant WhatsApp self-service."},{label:"Better parent satisfaction scores",body:"Parents prefer the institutes that proactively keep them informed. The messaging layer is part of the school's service standard."},{label:"Improved learner retention in edtech",body:"Scheduled engagement nudges and milestone celebrations reduce drop-off in self-paced courses."}],bestPractices:[{title:"Send fee reminders before due, not after",body:"A reminder 7 days before due, again 2 days before, and on the day, keeps payment cycles healthy. After-due-date reminders are recovery, not collection."},{title:"Localise critical messages to parent language",body:"Fee, attendance and emergency messages should go in the language the parent reads. Bilingual where needed."},{title:"Group parents by class for two-way chat",body:"A class WhatsApp group has its own dynamics. Per-class WhatsApp Business sender, with the class teacher as primary responder, scales better than one giant group."},{title:"Differentiate transactional vs marketing",body:"Admission marketing uses one sender ID and template category. Fee / attendance / result notifications use another. Don't mix them â the deliverability impact is real."},{title:"Confirm receipt of high-stakes updates",body:"For results, exam dates and unscheduled closures, ask parents to acknowledge with a tap. Confirms reach, surfaces parents whose number changed."}],implementation:[{title:"Connect to your school ERP",body:"A REST API and webhooks support most common school ERPs and fee-management systems. Connector specifics for Indian-market platforms can be confirmed with sales."},{title:"Multi-language template library",body:"Templates can be approved in major Indian languages once and reused. Per-student language preference triggers the right variant automatically."},{title:"Per-class / per-batch segmentation",body:"Push class, section, batch, course and roll number into the platform. Use them as audience filters for targeted messaging."},{title:"Sandbox for the academic calendar",body:"A sandbox lets the IT / academic team rehearse end-of-term result publishing or admission-cycle journeys before going live with the real student set."}
1],complianceNotes:"DLT-registered transactional templates, parental consent capture, and opt-out workflows that respect Indian data-protection norms.",complianceDetail:"Education communication is regulated by TRAI DLT for SMS, by WhatsApp Business policy for WhatsApp, and increasingly by the DPDP Act for handling of student / parent personal data. Ojiva AI handles each: DLT registration covers transactional and promotional templates separately; WhatsApp Business templates are approved through the standard Meta review; per-student / per-parent consent is captured at enrolment and tracked at the platform level so opt-outs are honoured. For institutions with younger learners, parental consent flows can be built into the enrolment journey itself.",faqs:[{q:"Can we send messages to parents and students from one platform?",a:"Yes â segments and template-level personalisation handle parent vs. student copy from the same campaign. Per-recipient relationship (mother / father / student / guardian) can be a segment field."},{q:"Does it integrate with our school ERP?",a:"A REST API and webhooks support most common ERPs and fee-management systems. Specific connector readiness for popular Indian-market school software can be confirmed with our team."},{q:"Can we automate admission counselling on WhatsApp?",a:"Yes â WhatsApp Business API supports two-way conversations, FAQ bots, document collection and human-agent handoff for warm leads. Common admission flows are templated."},{q:"How do we handle bounced or undeliverable messages?",a:"Delivery status is reported per message; failed records can be retried automatically on a fallback channel or flagged for manual follow-up by the admin team."},{q:"Can we send messages in regional languages?",a:"Yes â Unicode SMS supports major Indian scripts; WhatsApp and RCS templates can be approved in multiple languages once and reused per-recipient based on the language preference on file."},{q:"How do bus / transport notifications work?",a:"Per-route segments make it easy to message only the affected parents when a bus is delayed or rerouted. SMS goes first, voice fallback for urgent cases."},{q:"Can we run separate campaigns per branch?",a:"Yes â multi-branch / multi-campus institutes can have per-branch sender IDs, per-branch templates and per-branch user accounts, all under one parent organisation."},{q:"How are exam results published at scale?",a:"Bulk-publish through the API with a secure portal link per student. Templates support dynamic variables (name, roll number, exam) so every message is personalised."}]},{slug:"real-estate",name:"Real Estate",shortName:"Real Estate",icon:"bi-houses-fill",color:"#0ea5e9",eyebrow:"Real Estate & Property Solutions",headline:"WhatsApp & SMS for Real Estate Developers & Brokers in India",subtitle:"Deliver brochures instantly, automate site-visit reminders, send EMI alerts and keep buyers warm through the long post-booking cycle â using WhatsApp Business API and Bulk SMS.",intro:"Indian real estate is a long-cycle, high-value sale. The gap between first enquiry and registration can run months; between registration and possession, years. Across that span, every buyer touchpoint matters â the brochure delivery on enquiry day, the site-visit reminder, the EMI receipt, the construction-progress update, the possession-date confirmation. Ojiva AI gives developers, brokerages, REITs, plotted-development sales teams and project marketing agencies a single multi-channel layer to keep buyers warm and informed across SMS, WhatsApp Business API, RCS and Voice. Templates are DLT-registered, sales-team WhatsApp threads route through one business number (not personal), and per-project, per-stage segmentation handles the difference between a fresh enquiry and a registered booking.",painPoints:[{title:"Long sales cycles that drop off in silence",body:"Real-estate deals take months. Buyers go quiet, sales teams move on, and what started as a hot enquiry quietly evaporates. Without an automated nurture cadence, your CAC works much harder than
1it needs to."},{title:"Documentation flow that needs constant chase",body:"Booking forms, agreements, payment receipts, KYC documents, possession papers â every step needs documents to flow back and forth. Manual chase via phone burns sales-team hours and frustrates buyers."},{title:"Site visits that don't convert because of no-shows",body:"A scheduled site visit that doesn't happen wastes a sales-team afternoon and signals an uninterested buyer. The right reminder, on the right channel, dramatically reduces no-shows and protects sales-team utilisation."}],channelFit:[{channel:"sms",label:"Bulk SMS",use:"Site-visit reminders, EMI alerts & booking confirmations via Bulk SMS",body:"Reliable rail for transactional touchpoints â site-visit reminders, booking confirmation, EMI due / received, possession-stage updates. DLT-registered templates keep deliverability healthy."},{channel:"whatsapp",label:"WhatsApp API",use:"Brochure delivery, lead nurturing & two-way buyer chat on WhatsApp API",body:"Where the actual conversation happens. Brochure PDF, walkthrough video, pricing sheet, document collection, sales-team chat â all run on the WhatsApp Business API number, not personal phones."},{channel:"rcs",label:"RCS Messaging",use:"Rich project carousels & verified developer identity via RCS Messaging",body:"For supported devices, RCS lets the developer brand show up with verified sender, brand colours, and rich project carousels â useful for premium project marketing."},{channel:"voice",label:"Voice Call",use:"Site-visit confirmation IVR, satisfaction surveys & possession reminders",body:"Outbound voice for the touchpoints that need a human voice â site-visit confirmation IVR, post-booking feedback calls, possession-handover satisfaction surveys."}],useCases:[{title:"Site-visit nudges",body:"Confirm the visit on WhatsApp the day before, SMS reminder day-of, voice fallback if the buyer hasn't responded. Buyers can reschedule from the message itself with a tap."},{title:"Brochure & pricing share",body:"Send a WhatsApp message with brochure PDF, walkthrough video and current pricing the moment a fresh enquiry lands. Sales team gets a buyer who is already informed by the time they call."},{title:"Construction & possession updates",body:"Quarterly progress updates with photos, milestones and possession-date communication. Builds trust through the long gap between booking and handover."},{title:"EMI & payment reminders",body:"Pre-due, due, and overdue reminders across SMS and WhatsApp, with a voice-call fallback for the highest-value follow-ups. Receipts and acknowledgements automatically once payment lands."},{title:"Document collection on WhatsApp",body:"KYC documents, agreement signatures and proof-of-payment collected directly through WhatsApp media uploads. Eliminates the email-attachment back-and-forth."},{title:"Post-handover engagement",body:"Even after possession, the relationship continues â society maintenance, future-project pre-launch invitations, referral nudges. Stay in touch without spamming."}],outcomes:[{label:"Higher site-visit show-up rates",body:"Multi-touch reminders across WhatsApp and SMS reduce no-shows and protect sales-team utilisation."},{label:"Faster document turnaround",body:"Document collection on WhatsApp closes the loop faster than email-attachment chase, especially for KYC and signed agreements."},{label:"Better buyer trust through long cycles",body:"Quarterly construction updates with photos and milestones build confidence through the long gap between booking and possession."},{label:"Sales-team WhatsApp without personal numbers",body:"A single WhatsApp Business number handles all buyer chat, with per-buyer routing to the assigned sales agent. Personal numbers stay personal."},{label:"Cleaner referral pipeline",body:"Happy buyers refer others. A polite post-possession nudge, with an easy referral-share link, surfaces a referral pipeline that would otherwise stay invisible."}],bestPractices:[{title:"Send the brochure within minutes of enquiry capture",body:"The first 15 minutes are when the buyer is most engaged. A WhatsApp brochure delivery in that window outperforms a 24-hour-later sales call."},{title:"Time site-visit reminders to the visit window",body:"Day-before reminder for confirmation, day-of reminder for show-up, follow-up after no-show to reschedule. Don't spam â three touches max."},{title:"Use per-project sender IDs",body:"Each project should have its own DLT sender ID and templates. Cross-project messaging and audit get cleaner; brand presentation stays project-specific."},{title:"Keep sales-team WhatsApp on a business number",body:"Personal-number WhatsApp doesn't scale and doesn't leave your control when an agent leaves. WhatsApp Business API on one number, with per-agent routing, does both."},{title:"Don't over-message during construction",body:"Quarterly construction-progress updates are appreciated. Weekly ones aren't. Match cadence to milestone, not to internal sales urgency."}],implementation:[{title:"Connect your CRM / lead-capture",body:"A webhook from your lead-capture / CRM can trigger a WhatsApp template the moment a new lead is created â no manual hand-off needed."},{title:"WhatsApp Business API on one number",body:"WhatsApp Business API runs on a single business number. Internal routing assigns each conversation to a sales agent, with full audit trail and supervisor visibility."},{title:"Multi-project architecture",body:"Per-project sender IDs, templates and reporting under one parent account. Per-project user roles for sales teams."},{title:"Document handling",body:"WhatsApp media and RCS attachments support PDFs, images and videos with delivery tracking. Storage and retention policies can be aligned to your compliance requirements."}],complianceNotes:"DLT-ready for transactional reminders. Promotional traffic respects opt-out and template-approval rules under TRAI guidelines.",complianceDetail:"Real-estate communication mixes regulated transactional flows (booking confirmation, EMI receipt, possession notification) with promotional flows (project launch, pre-launch invitations, referral asks). Ojiva AI separates them at the DLT-template level, keeps opt-out
1s distinct between the two, and provides per-template audit logs that can be filtered by project, sender ID or campaign. For developers running multi-state operations, per-state DLT considerations are handled as part of onboarding.",faqs:[{q:"Can leads from a portal flow straight into a WhatsApp drip?",a:"Yes â a webhook from your lead-capture / CRM can trigger a WhatsApp template the moment the lead is created. The brochure, walkthrough video and pricing can be sent automatically before the sales team even calls."},{q:"Can sales teams chat on WhatsApp without giving out personal numbers?",a:"Yes â WhatsApp Business API runs on a single business number. Internal routing assigns each conversation to a sales agent, with supervisor visibility and an audit trail that survives agent churn."},{q:"How are documents shared securely?",a:"WhatsApp media and RCS attachments support PDFs, images and videos with delivery tracking. KYC and signed agreements can be collected through the same channel with timestamped receipts."},{q:"Can I send updates only to buyers who paid the booking amount?",a:"Yes â segment by stage in the funnel (enquiry, site-visited, booked, registered, under-construction, possession) and target only buyers in a specific milestone group."},{q:"Will the platform scale across multiple projects?",a:"Yes â multi-project setups are common; per-project sender IDs, templates and analytics keep reporting clean. Sales-team users can be scoped to one or many projects."},{q:"Can I run pre-launch campaigns to past buyers?",a:"Yes â past buyers who consented to marketing can be a segment. Pre-launch RCS or WhatsApp campaigns to that audience often outperform paid digital, with much better economics."},{q:"How do I track whether a buyer opened the brochure?",a:'Webhook events report delivery, read and click for trackable links inside the message. The CRM can show "opened brochure twice" before a sales agent dials the buyer.'},{q:"Are there templates pre-approved for real-estate use cases?",a:"A starter library of common real-estate templates (site-visit confirmation, brochure delivery, EMI reminder, possession update) is available. Custom templates with your project copy can be approved as part of onboarding."}]},{slug:"travel-hospitality",name:"Travel & Hospitality",shortName:"Travel & Hospitality",icon:"bi-airplane-fill",color:"#0891b2",eyebrow:"Travel & Hospitality Solutions",headline:"Hotel & Travel Guest Messaging on WhatsApp & SMS in India",subtitle:"Send instant booking confirmations, check-in nudges, boarding reminders and post-stay review requests â across SMS, WhatsApp Business API, RCS and Voice for airlines, hotels and OTAs.",intro:"Indian travel and hospitality is a multi-step, time-critical journey. From booking confirmation to check-in, from boarding-pass delivery to post-stay reviews, every message needs to land in seconds, often across multiple languages and time zones. Ojiva AI gives airlines, OTAs, hotels and resort chains, IRCTC integrators, bus and rail aggregators, and tour operators a single platform that handles the full lifecycle â booking confirmation, payment receipt, check-in nudge, boarding-pass delivery, itinerary change, gate / room change, post-stay review and re-booking nudge. Templates work in major Indian languages, transactional bursts during sale events are sized for, and WhatsApp two-way concierge support handles the moments where automation isn't enough.",painPoints:[{title:"Time-critical alerts that cannot wait",body:"Gate change, flight delay, cancellation, hotel-room reassignment â these messages have to arrive in seconds. A delayed gate-change SMS is a missed flight. The platform behind it has to be sized for that bar."},{title:"Multi-language guests at scale",body:"Indian travellers expect content in their language. International inbound tourists expect it in theirs. Manual translation doesn't scale; per-language templates approved once and reused per-guest do."},{title:"Post-stay engagement that gets neglected",body:"Reviews, loyalty enrolment and re-booking nudges often get neglected once the guest has left. The result is leaving repeat-purchase economics on the table."}],channelFit:[{channel:"sms",label:"Bulk SMS",use:"Booking confirmations, check-in nudges & itinerary alerts via Bulk SMS",body:"Reliable rail for transactional travel touchpoints â booking confirmation, payment receipt, check-in OTP, itinerary changes. DLT-registered templates handle Indian operator delivery."},{channel:"whatsapp",label:"WhatsApp API",use:"Two-way WhatsApp concierge for bookings, itinerary changes & guest support",body:"Where richer guest interactions live â two-way concierge support, boarding pass delivery as a media attachment, group-booking coordination, restaurant and spa reservations."},{channel:"rcs",label:"RCS Messaging",use:"Rich boarding passes, hotel amenity cards and check-in buttons via RCS",body:"For supported devices, RCS adds verified sender, brand colours and rich itinerary cards. Useful for premium airline / hotel brands where in-inbox presentation matters."},{channel:"voice",label:"Voice Call",use:"Check-in reminder calls, upsell IVR & post-stay satisfaction surveys",body:"Automated voice for cancellation flows, multi-language schedule-change announcements, and high-volume disruption events where SMS and WhatsApp queues are saturated."}],useCases:[{title:"Booking confirmations",body:"Instant SMS + WhatsApp confirmation with PNR / booking ID, e-ticket and check-in deep link. Guest gets the message before they put the phone down."},{title:"Check-in & boarding",body:"Pre-flight check-in nudges, boarding-pass delivery on WhatsApp, gate-change alerts the moment the change is published. Reduces gate-counter chaos and missed boarding events."},{title:"Itinerary changes",body:"Schedule changes, hotel reassignments, layover updates and cancellation flows with re-booking links. Guests reach a human agent on WhatsApp if needed."},{title:"Post-stay reviews",body:"Day-after WhatsApp review request with a one-tap rating and follow-up promo for the next stay / next trip. Builds review volume passively and surfaces issues early."},{title:"Loyalty and re-booking",body:"For loyalty members, segment-targeted offers â birthday upgrades, milestone perks, dormant-member win-back. Higher engagement than a generic newsletter."},{title:"Group-booking coordination",body:"For weddings, corporate offsites or tour groups, a shared WhatsApp thread coordinates all participants â itinerary, room allocation, transfer details â without WhatsApp groups breaking."}],outcomes:[{label:"Faster guest response to disruptions",body:"Schedule-change messages land in seconds, not minutes â guests can replan before reaching the airport / hotel desk."},{label:"Lower call-centre load during peaks",body:"WhatsApp self-service handles routine check-in, room-status and re-booking queries that would otherwise hit the call centre."},{label:"Higher post-stay review volume",body:"A simple post-stay WhatsApp request collects feedback at scale â both for issue triage and for OTA / Google review pipeline."},{label:"Better re-booking conversion",body:"Segment-targeted re-booking nudges to past guests outperform generic promotional blasts in both engagement and conversion."},{label:"Cleaner brand experience",body:"Verified senders, branded RCS cards and consistent template voice keep every message looking like the brand, not the aggregator."}],bestPractices:[{title:"Match channel to message urgency",body:"Schedule changes need SMS speed. Itinerary detail can be WhatsApp. Loyalty offers can be RCS. The right channel makes the difference between read and ignored."},{title:"Localise template variants",body:"Same template, multiple language variants. Trigger the right one based on the booking-channel language preference. Don't default everyone to English."},{title:"Use WhatsApp for boarding-pass delivery",body:"Boarding passes as PDF attachments on WhatsApp are easier to retrieve than email. Both channels work; WhatsApp tends to win."},{title:"Send the post-stay review while it's fresh",body:"Day-after-stay is the right window. A week later, the guest has moved on and the response rate drops sharply."},{title:"Surface human handoff in concierge chat",body:"Bots handle the easy 80%. The remaining 20% â special requests, complaints, complex re-bookings â should hand off to a human agent quickly and visibly."}],implementation:[{title:"PMS / GDS / OTA integration",body:"A REST API and webhooks
1support most travel-tech stacks. Booking, payment and itinerary events trigger the right messaging flows. Specific connector readiness can be confirmed with our team."},{title:"Multi-property setups",body:"For chain hotels and multi-route airlines, per-property / per-route sender IDs, templates and reporting under one parent account."},{title:"Bot + agent handoff",body:"WhatsApp Business API supports bot-to-agent handoff for live concierge support. Agents see full conversation context when they pick up."},{title:"Throughput for sale spikes",body:"Throughput is sized for transactional bursts. Enterprise plans include dedicated routes for predictable peaks like festive sales and long-weekend bookings."}],complianceNotes:"Templates can be approved in multiple Indian languages. Transactional traffic registered on DLT for clean delivery to operator networks.",complianceDetail:"Travel communication is largely transactional but does include marketing and re-booking nudges. Ojiva AI handles both: transactional templates (booking confirmation, schedule change, check-in OTP) are registered separately from marketing templates (sale offers, loyalty perks), opt-outs are distinct, and per-template audit logs help operators support a high message-volume programme without surprises.",faqs:[{q:"Can I send messages in multiple Indian languages?",a:"Yes â Unicode SMS, WhatsApp and RCS support major Indian scripts; templates can be approved per language and routed by guest preference. Useful for both domestic regional language coverage and inbound international traveller languages."},{q:"Will it integrate with our PMS or GDS?",a:"A REST API and webhooks support most travel-tech stacks. Specific connector readiness for the major Indian PMS / GDS / OTA platforms can be confirmed with our team during scoping."},{q:"Can travellers reach a human via WhatsApp?",a:"Yes â WhatsApp Business API supports bot-to-agent handoff for live concierge support. Agents see full conversation context, attachments and prior interactions when they pick up the chat."},{q:"How do we handle high-volume booking confirmations?",a:"Throughput is sized for transactional bursts. Enterprise plans include dedicated routes for predictable peaks (festive sales, long weekends, sale events) so confirmations don't queue up in the busy hours."},{q:"Can I send branded RCS messages?",a:"Yes â RCS supports verified sender, brand colours, logos and rich cards on supported Android devices. Useful for premium airline and hotel brands where in-inbox brand presentation matters."},{q:"How are boarding passes / e-tickets delivered?",a:"Boarding passes and e-tickets can be delivered as PDF attachments on WhatsApp, with a deep-link to add to wallet. SMS carries the URL; WhatsApp carries the file."},{q:"Can we run loyalty-member campaigns?",a:"Yes â loyalty-member segments are first-class. Birthday offers, tier-upgrade perks, dormant-member win-back and milestone celebrations can each have their own template and audience."},{q:"How do we handle disruptions (mass cancellations, weather)?",a:"Bulk voice and SMS broadcasts cover the affected cohort fast. WhatsApp interactive buttons let travellers self-serve re-booking, with overflow into a live agent queue."}]},{slug:"logistics-delivery",name:"Logistics & Delivery",shortName:"Logistics & Delivery",icon:"bi-truck",color:"#f59e0b",eyebrow:"Logistics & Last-Mile Delivery Solutions",headline:"Shipment Tracking & Delivery OTP for Logistics in India",subtitle:"Cut RTO rates, send live out-for-delivery alerts, confirm OTP at handover and let customers reschedule via WhatsApp â for 3PLs, e-commerce logistics and hyperlocal delivery fleets.",intro:"Indian logistics and last-mile delivery operates at scale where small percentage improvements translate into significant margin. A 2% reduction in RTO across a million orders is real money. A faster pickup-to-delivery message lifecycle is real CX. Ojiva AI gives 3PL operators, e-commerce in-house logistics teams, hyperlocal delivery platforms, quick-commerce companies and B2B logistics aggregators a single multi-channel layer for every shipment touchpoint â pickup confirmation, hub-in / hub-out, out-for-delivery, OTP at handover, delivery confirmation with photo proof, return / reschedule flow and rider-customer call masking. Built to handle festive-season peaks without dropping messages, with template hygiene that keeps delivery rates clean across operators.",painPoints:[{title:"High RTO that eats unit economics",body:'Returns to origin destroy the unit economics on lower-AOV orders. The biggest driver â "buyer not available" failures â is exactly what pre-delivery confirmation messages prevent. Even a small reduction compounds across volume.'},{title:"Low driver-customer trust at the doorstep",body:"Customers want to know who is at the door. A verified-sender notification just before delivery, with rider name and number, builds confidence and reduces refused deliveries."},{title:"Volume spikes that strain the messaging stack",body:"Festive seasons, sale events and quarter-end peaks need a stack that scales without queueing. Throughput, route diversity and operator routing all need to be sized for the worst hour, not the average."}],channelFit:[{channel:"sms",label:"Bulk SMS",use:"Pickup confirmation, shipment tracking & delivery OTP via Bulk SMS",body:"Default rail for high-volume transactional logistics traffic â pickup confirmed, hub events, out-for-delivery, OTP at handover, delivered confirmation. DLT-registered with route diversity for peak handling."},{channel:"whatsapp",label:"WhatsApp API",use:"Real-time WhatsApp delivery alerts, reschedule flows & riderâcustomer connect",body:"Where buyer interaction lives â reschedule flows with interactive buttons, two-way chat for delivery questions, photo proof of delivery sent directly to the buyer."},{channel:"rcs",label:"RCS Messaging",use:"Rich RCS delivery cards with live tracking links and confirmed-delivery badges",body:"For supported devices, RCS adds verified sender, brand colours, rich delivery cards with map, ETA and rider details. Useful for premium logistics brands where the doorstep experience starts in the inbox."},{channel:"voice",label:"Voice Call",use:"Delivery confirmation IVR, OTP fallback calls & post-delivery feedback",body:"Outbound voice for delivery-confirmation IVR (especially COD), and number-masked rider-customer connect that hides personal numbers on both sides while preserving call records."}],useCases:[{title:"Pickup-to-delivery alerts",body:"Automated lifecycle messages for pickup, hub-in, hub-
1out, out-for-delivery and delivered. Buyer always knows where the package is without asking."},{title:"OTP at delivery",body:"Single-channel or multi-channel OTP at the moment of handover for high-value packages. Multi-channel fallback (SMS â WhatsApp â Voice) keeps delivery moving even when one channel is degraded."},{title:"Reschedule on WhatsApp",body:"Customer can reschedule a missed delivery via interactive buttons, reducing failed second attempts and RTO. Rider gets the new slot without back-and-forth via dispatch."},{title:"Riderâcustomer call masking",body:"Voice connect that hides personal numbers on both sides, with call recording for audit. Protects driver privacy and customer privacy equally."},{title:"Photo proof of delivery",body:"Rider app captures a photo of the delivered package; the platform sends it to the buyer over WhatsApp as soon as the delivery is marked complete. Reduces dispute volume sharply."},{title:"Return-pickup coordination",body:"For returns and exchanges, the buyer schedules the pickup directly via WhatsApp button, the rider gets the new task automatically, and confirmation lands when the return is collected."}],outcomes:[{label:"Lower RTO percentages",body:'Pre-delivery confirmation flows reduce "buyer not available" failures and protect margins on COD and first-attempt orders.'},{label:"Higher first-attempt delivery success",body:"Same-day reminder + reschedule-button + voice fallback combine to push first-attempt success rates up."},{label:"Reduced dispute volume on POD",body:'Photo-proof of delivery sent to the buyer eliminates "I never received it" disputes.'},{label:"Better driver privacy and CX",body:"Number-masked rider-customer voice connect protects both parties while preserving call records for audit."},{label:"Scaling without breakages on peak days",body:"Festive-season throughput sized for worst-hour handles Diwali / EoSS / sale events without messages dropping or queueing."}],bestPractices:[{title:"Confirm COD intent before pickup",body:"For COD orders, a same-day WhatsApp confirmation before pickup is the single highest-leverage RTO-reduction step."},{title:"Send out-for-delivery with rider details",body:"Rider name + photo + masked number in the out-for-delivery message dramatically increases doorstep-acceptance rates."},{title:"Use interactive reschedule for missed attempts",body:'A WhatsApp message with "reschedule" / "leave at gate" / "cancel" buttons converts more missed attempts into successful deliveries than a voice IVR does.'},{title:"Capture photo POD on every delivery",body:"A timestamped, geotagged photo POD sent to the buyer is the cheapest insurance against dispute volume."},{title:"Pre-warm festive routes",body:"Coordinate with operators ahead of festive seasons to ensure dedicated routes are warm and ready. Don't discover capacity issues on Diwali eve."}],implementation:[{title:"WMS / OMS integration",body:"A REST API and webhooks let your warehouse / order-management system trigger lifecycle events. Specific connector readiness for popular Indian logistics-tech stacks can be confirmed with our team."},{title:"Number masking setup",body:"Voice number-masking for rider-customer connect is provisioned per project, with per-call audit and recording where consent allows."},{title:"Multi-channel OTP at delivery",body:"OTP API at delivery handles channel selection automatically based on the buyer's reachability profile. Multi-channel fallback keeps delivery moving."},{title:"Peak-season scoping",body:"For festive / sale-event peaks, throughput and dedicated-route capacity are scoped in advance with the solutions team. Sandbox dry-runs validate the load."}],complianceNotes:"DLT-registered for transactional flows. Number-masking voice connects are designed with privacy and recording-consent in mind.",complianceDetail:"Logistics communication is overwhelmingly transactional and subject to standard TRAI DLT requirements. Where it gets nuanced is in voice number-masking â Ojiva AI provisions number masking with per-call audit, with recording-consent flows where applicable. For high-volume operations with multiple business entities (e.g., logistics arm of an e-commerce parent), per-entity DLT registration and template separation are handled as part of onboarding.",faqs:[{q:"Can the platform handle festive-season peaks?",a:"Yes â throughput is sized for high transactional bursts. Enterprise plans add dedicated routes for predictable spikes like Diwali, EoSS and sale-event peaks. Sandbox dry-runs validate capacity before the season."},{q:"Is riderâcustomer call masking supported?",a:"Yes â voice connects can mask both numbers, route calls through a single business number, and capture call records. Per-call audit logs are queryable."},{q:"Can customers reschedule via WhatsApp?",a:"Yes â WhatsApp interactive buttons let buyers confirm, reschedule, leave-at-gate, or cancel without contacting support. Rider gets the updated slot automatically."},{q:"How does delivery proof work?",a:"Photo proofs and OTP confirmations can be captured by the rider app and sent to the customer immediately. Timestamped, geotagged POD records reduce dispute volume sharply."},{q:"Can we white-label the messages with our brand?",a:"Yes â registered DLT sender IDs, RCS verified sender and WhatsApp Business profiles all carry your brand. Per-project sender IDs are common for multi-brand logistics operators."},{q:"How does multi-channel OTP at delivery work?",a:"A single OTP API call routes across SMS / WhatsApp / Voice based on the buyer's reach
1ability profile. Multi-channel fallback keeps delivery moving even when one channel is degraded for a specific user."},{q:"Can we run separate flows per fleet / per zone?",a:"Yes â flows can be scoped per fleet, per zone, per city or per project. Templates and reporting follow the same scoping so each business unit sees its own metrics."},{q:"How are returns handled differently from forward shipments?",a:"Reverse-logistics flows can use a separate template set and a separate sender ID. Buyer schedules pickup via WhatsApp, rider gets the task, confirmation lands on collection."}]},{slug:"insurance",name:"Insurance",shortName:"Insurance",icon:"bi-shield-check",color:"#dc2626",eyebrow:"Insurance Communication Solutions",headline:"WhatsApp & SMS for Insurance Renewals & Claims in India",subtitle:"Reduce lapsed policies, automate renewal reminders, send claim status updates and speed up e-KYC nudges â across SMS, WhatsApp Business API and Voice for life, health and motor insurers.",intro:"Indian insurance â life, general, health, motor â is a long-cycle, low-frequency, high-trust product. The communication layer is part of the experience: a missed renewal reminder is a lapsed customer, a confused claim status is an angry customer, an unclear KYC nudge is a stuck onboarding. Ojiva AI gives insurers, brokers, web aggregators, MGAs and bancassurance partners a single multi-channel platform for every policy-lifecycle touchpoint â quote follow-up, e-KYC nudges, policy issuance, premium reminders, renewal cadence, claim status updates and post-claim NPS. Templates are designed to carry the disclosures that regulated insurance communication requires, and per-product / per-channel separation keeps the audit story clean.",painPoints:[{title:"Renewal lapse that compounds across the book",body:"A missed renewal reminder is a lapsed policy. Multiplied across a large book, lapse hurts retention, embedded value and the next year's sales target. The right reminder cadence is one of the cheapest retention levers available."},{title:"Claims communication that customers struggle to follow",body:"Customers want clarity at every step of a claim â claim received, document required, surveyor assigned, settlement done. Manual phone-call updates don't scale, and silence between steps causes calls to come into the contact centre."},{title:"Compliance and disclosure that has to be perfect",body:"Templates need to carry mandated disclosures, opt-outs and consent â every single time, in the right format. Errors here are not cosmetic; they're regulator-visible."}],channelFit:[{channel:"sms",label:"Bulk SMS",use:"Premium reminders, policy issuance & renewal alerts via DLT Bulk SMS",body:"Default rail for transactional policy traffic â premium due / received, policy issued, KYC OTP, claim status. DLT-registered with insurance-specific template support."},{channel:"whatsapp",label:"WhatsApp API",use:"Two-way WhatsApp for claim status, KYC completion & policy renewal",body:"Where richer interactions live â quote-follow-up drips, e-KYC document collection through WhatsApp media, claims-status chatbot, post-claim NPS."},{channel:"rcs",label:"RCS Messaging",use:"Verified branded RCS messaging for insurance policy communication",body:"For supported devices, RCS adds verified insurer brand and rich card layout for premium policies, renewal offers and certificate delivery."},{channel:"voice",label:"Voice Call",use:"Renewal reminder calls, claim update IVR & satisfaction surveys",body:"Outbound voice for renewal-reminder IVR on the highest-value policies, post-claim satisfaction calls, and missed-OTP recovery flows."}],useCases:[{title:"Quote-to-policy nudge",body:'Drip campaign across WhatsApp + SMS to convert generated quotes into bound policies. Right-channel-right-moment cadence outperforms a generic "still interested" call from the agent.'},{title:"Renewal reminders",body:"Pre-due, due, and grace-period reminders across multiple channels. Per-policy customisation by line-of-business â health renewals look different from motor renewals."},{title:"Claims status updates",body:"Lifecycle messages for claim received, document required, surveyor assigned, settlement done. Customer always knows where they are; contact-centre call volume drops."},{title:"KYC & document collection",body:"WhatsApp-driven document upload to complete e-KYC without portal logins. Surveyor reports, medical reports and proof-of-income docs all flow back over WhatsApp media."},{title:"Premium reminders & receipts",body:"Pre-due, due-day and post-due-date reminder cascade with payment links inside the message. Receipts go out immediately on payment."},{title:"Cross-sell on policy events",body:"Birthday upgrades, life-event-triggered offers, post-claim winback, and family-policy add-ons â all timed to events that matter, not generic promotional bursts."}],outcomes:[{label:"Higher renewal retention",body:"Multi-touch renewal reminder cadences across SMS and WhatsApp lift renewal rates compared to single-channel reminders."},{label:"Faster e-KYC and document collection",body:"WhatsApp document upload closes onboarding loops faster than email or portal upload, especially for less tech-fluent customers."},{label:"Lower contact-centre load on claims",body:'Proactive lifecycle status updates remove the most common inbou
1nd query â "what\'s the status of my claim?".'},{label:"Better cross-sell conversion",body:"Event-triggered cross-sell on real-life moments (birthday, life event, claim-completion) outperforms generic offer broadcasts."},{label:"Cleaner regulator audit story",body:"Per-template approval records, per-message delivery logs and per-customer consent state make audits a query, not a fire-drill."}],bestPractices:[{title:"Send renewal reminders before, not after",body:"Pre-due reminders prevent lapse. Post-due reminders are recovery. The cheapest renewal is the one that never lapsed in the first place."},{title:"Use WhatsApp for KYC document upload",body:"Customers struggle with portal uploads. WhatsApp media upload is universally understood and works on every smartphone."},{title:"Surface every claim-status change in real time",body:"A status change without notification is a contact-centre call waiting to happen. Wire every state change in the claim system to a customer message."},{title:"Keep mandated disclosures in approved templates",body:"Disclosure copy lives in the template, not in the campaign. Approve once, reuse forever, audit easily."},{title:"Differentiate retail vs corporate communication",body:"Retail customers want simplicity. Corporate intermediaries want detail. Use separate sender IDs and template sets so the voice fits the audience."}],implementation:[{title:"Policy admin system integration",body:"A REST API and webhooks support most policy admin systems used by Indian insurers. Policy events trigger the right messages without manual queue management."},{title:"Multi-LOB template architecture",body:"Per-LOB (health, motor, life, general) sender IDs and templates under one parent account. Reporting separates by line-of-business automatically."},{title:"Disclosure-ready templates",body:"Templates can carry the disclosures regulated insurance communication requires. Onboarding includes assistance designing approval-ready templates that meet IRDAI expectations."},{title:"Contact-centre chatbot handoff",body:"WhatsApp chatbots handle FAQ-style claim and renewal queries; complex queries hand off to a human agent in the contact centre with full context."}],complianceNotes:"Templates can carry the disclosures that regulated insurance communication requires. DLT registration and opt-out workflows enforced.",complianceDetail:"Insurance communication has to balance two regulators â TRAI for the messaging layer (DLT, sender IDs, opt-outs) and IRDAI for the content (disclosures, distance-marketing rules, customer-consent rules). Ojiva AI handles both: DLT registration covers transactional and promotional templates separately, opt-outs are honoured, and templates are designed to carry the disclosures IRDAI expects. Per-template audit logs make regulator-response queries tractable. For insurers running multiple lines of business under one parent organisation, per-LOB DLT registration and template separation are handled as part of onboarding.",faqs:[{q:"Can I bring my own templates with mandated disclosures?",a:"Yes â templates with disclosure copy can be registered on DLT and used unchanged across SMS, WhatsApp and RCS. Onboarding includes assistance translating your existing disclosure-ready copy into approval-ready templates."},{q:"Does the platform integrate with my policy admin system?",a:"A REST API and webhooks support most policy admin systems used by Indian insurers. Specific connector readiness can be confirmed with our solutions team."},{q:"Can a claims chatbot handle FAQs on WhatsApp?",a:"Yes â WhatsApp Business API supports interactive bots for status checks and FAQ resolution, with handoff to a human agent for complex queries. Bots can be wired to your claims system for live status."},{q:"Will it work for both retail and corporate insurance?",a:"Yes â the same platform supports retail customers and corporate intermediaries with separate sender IDs, templates and reporting. Voice and tone differ between the two; templates and routing handle that."},{q:"How are KYC documents handled?",a:"Documents are sent over WhatsApp media or secure links, with timestamped delivery / read receipts. Storage and retention policies can be aligned to your compliance team's requirements."},{q:"Can we send renewal cadences per line-of-business?",a:"Yes â health renewals, motor renewals, life renewals can each have their own template, cadence and channel mix. Per-LOB reporting keeps insights separate."},{q:"How do we handle multi-state regulatory differences?",a:"For insurers operating across states with different regulatory nuances, per-state template variants and routing can be configured. The solutions team helps scope per-state requirements during onboarding."},{q:"Can we run cross-sell campaigns to existing customers?",a:"Yes â opted-in existing customers form a segment, with cross-sell templates approved separately from transactional. Event-tr
1iggered cross-sell (birthday, life event, post-claim) outperforms generic broadcasts."}]}]],82628)}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.