Frequently asked questions

Nucleus Ai is a business automation and software company in Noida, India that builds customer messaging and web systems: official WhatsApp Business API setup, RCS business messaging, AI chatbot automation, SEO, website development and custom SaaS products. The common thread is conversation — getting a business found, then answering, qualifying and selling automatically on the channels its customers already use.

Nucleus Ai Automation Private Limited is registered in India under CIN U63111UW2026PTC255078 and operates from Unit 603–604, 6th Floor, Tower B, Bhutani Alphathum, Sector 90, Noida, Gautam Buddha Nagar, Uttar Pradesh 201305. We work with businesses across India and support conversations in English, Hindi and Hinglish.

Yes. Nucleus Ai Automation Private Limited is a private limited company incorporated in India, and its CIN (U63111UW2026PTC255078) can be verified on the Ministry of Corporate Affairs register. Every invoice, contract and legal page on this site is issued in that name.

We work with businesses that have enough customer conversations for automation to pay for itself — typically retail and D2C brands, clinics and healthcare practices, education providers, real estate, hospitality and B2B service firms. The deciding factor is conversation volume and intent to sell on messaging channels, not company size or headcount.

Our systems, contracts and compliance work are built around Indian regulation — TRAI, DLT and the DPDP Act — so India is where we are strongest. WhatsApp Business API, chatbots, SEO, websites and SaaS development are not geographically limited, so international engagements are possible; RCS and SMS are, because those depend on Indian carrier registration.

It is how our services divide. Connect puts your brand on the channels customers already use — WhatsApp Business API and RCS. Automate answers, qualifies and sells without waiting for office hours — chatbots and workflow automation. Grow makes you the answer when someone searches for what you sell — SEO, websites and custom software. Most clients need more than one.

The WhatsApp Business API is Meta’s official platform for businesses that need to message at scale, and unlike the free WhatsApp Business app it has no device limit, supports multiple agents on one number, and allows automated template messages, catalogs and payment flows. The free app is designed for one person on one phone; the API is designed for a team, a CRM and thousands of conversations. Green-tick verification is only available through the API.

The green tick marks an Official Business Account and is granted by Meta at its sole discretion — it is not something an agency can buy or guarantee. Meta assesses brand notability, business authenticity and consistency of your business information across your website, public records and press coverage. Nucleus Ai prepares and submits the application end to end, fixes what is in our control, and resubmits if Meta declines.

Account setup and number verification are usually the fastest part; the variable is Meta’s own review of your business verification and any message templates, which is outside our control. We give you a realistic timeline in writing at the start of the engagement rather than a fixed promise we cannot enforce, and we tell you immediately if Meta comes back with questions.

There are two separate costs: our setup and management fee, quoted in a written statement of work, and Meta’s own per-conversation charges, which are billed by Meta at their published rates and passed through to you at cost. Meta prices conversations by category — marketing, utility, authentication and service — and rates differ by country. We show both lines separately so you always know what is ours and what is Meta’s.

Usually yes, provided the number is not already registered to a personal WhatsApp or WhatsApp Business app account. If it is, the number has to be deleted from that account first, and any chat history on it will not transfer to the API. Many businesses prefer to start with a fresh number so the existing one keeps working during migration.

Template messages are pre-approved message formats required for any conversation your business starts outside the 24-hour customer service window — order updates, delivery alerts, reminders and offers. Meta reviews each template to prevent spam and misleading content. We write and submit templates, and rework any that are rejected.

Yes. Payment flows can be built into the conversation using UPI links or payment-gateway links, so a customer goes from “I want it” to “paid” without leaving the thread. The gateway and its charges are yours; we build the flow and connect it to your order system.

Yes — that is one of the main reasons to move to the API. A shared team inbox puts every agent on the same number with conversation assignment, internal notes and full history, so nothing depends on whose phone a chat happens to be on.

When a customer messages your business, a 24-hour window opens during which you can reply freely with any content, at no per-message charge beyond the conversation itself. Outside that window you can only start a conversation using a pre-approved template message. This is why a WhatsApp strategy built on getting customers to message you first is cheaper and far less restricted than one built on broadcasting to them.

Collect consent at a point where the customer is deliberately asking to hear from you — a checkout checkbox that is not pre-ticked, a website opt-in page, a click-to-WhatsApp ad, or a QR code in-store — and keep a record of what they agreed to and when. Buying a list of numbers is not consent, and using one is the fastest way to get an account restricted. Our own messaging opt-in page is a working example of the standard we build to.

Meta assigns your number a quality rating based largely on how recipients react — blocks and "report" taps push it down, engagement holds it up. A low rating reduces your messaging limits and can lead to restrictions. It is driven by list quality and message relevance far more than by volume, which is why we push back on broadcasting to unengaged contacts.

Meta applies a messaging limit that starts low and increases as your number demonstrates good quality and consistent volume. New accounts are deliberately constrained, so a large first-day campaign is not possible regardless of what you pay. We plan the ramp so limits rise ahead of your campaign calendar rather than blocking it.

Restrictions almost always follow from message content, missing opt-in consent, or a low quality rating caused by users blocking or reporting your messages. We help you diagnose the cause, appeal where there are grounds, and fix the underlying practice. Where a suspension results from content you supplied or consent you did not obtain, responsibility sits with you under our Terms — which is exactly why we insist on documented opt-in from the start.

They are two different channels that happen to arrive in the same app. Text SMS is plain text with no images, no buttons and no branding beyond a six-character sender ID, and it works on every handset ever made. RCS is a richer protocol that shows your verified brand name and logo, supports images, product carousels, tap-to-reply buttons and read receipts, but only works where the handset, the operating system and the carrier all support it. RCS is not "SMS with pictures" — it is a separate channel that falls back to SMS when it cannot be delivered.

Match the channel to the message and the audience. Use WhatsApp for two-way conversation, catalogues and payments with customers who already use it. Use RCS for branded, visual campaigns to Android users without asking them to install anything. Use text SMS for anything that must arrive on any handset regardless of internet or app — OTPs, order updates, payment confirmations. Use voice for audiences who do not read comfortably in your language or do not use a smartphone. Most businesses run two or three, not one.

Yes, and it is usually the right answer. A common pattern is RCS first for the branded version, automatic SMS fallback for handsets that cannot receive it, and a voice broadcast for the segment that responds to neither. Another is WhatsApp for conversation and SMS purely for OTPs and transactional alerts. We design the routing so the same person does not receive the same message three times.

Text SMS and voice reach the most handsets, because both work on every phone in service with no app, no data connection and no smartphone. RCS reaches only handsets that support it. WhatsApp reaches only people who use WhatsApp — an enormous number in India, but not everyone. If universal reach is the requirement, SMS and voice are the only two channels that guarantee it.

It depends on volume and message type, and the honest answer is that per-message price is the wrong comparison. SMS is billed per message, WhatsApp per 24-hour conversation, RCS per message or session depending on the carrier, and voice by connected call duration. A single WhatsApp conversation can carry twenty messages for one charge, which makes it cheaper than SMS for real back-and-forth and more expensive for a one-line alert. We quote the operator cost and our fee as separate lines so you can compare properly.

Yes. Every commercial message in India requires documented prior consent, and the rules differ by channel: WhatsApp falls under Meta’s Business Messaging Policy, while RCS, SMS and commercial voice fall under TRAI’s Telecom Commercial Communications Customer Preference Regulations and the DLT framework. Consent must be specific, freely given and withdrawable — the Digital Personal Data Protection Act, 2023 also requires that withdrawing be as easy as opting in. Nucleus Ai collects consent per channel and honours STOP immediately.

DLT (Distributed Ledger Technology) registration is mandatory under TRAI’s regulations for any business sending commercial SMS, RCS or voice broadcasts in India. You register as a Principal Entity, register your headers (sender IDs) and your content templates, and record consent templates. Without it, messages are simply rejected by the operators. Nucleus Ai prepares and files the registration, headers and templates for you, but the DLT account is held in your name — the legal responsibility for what is sent stays with the business sending it.

Replying STOP works on WhatsApp, RCS and SMS, and we action it immediately across every channel that person is on. RCS messages can also carry a one-tap unsubscribe action. For commercial SMS and voice calls a recipient can additionally register on the national Do Not Disturb registry via 1909, independently of anything they have told us. Our messaging opt-in page documents the exact route for each channel.

RCS (Rich Communication Services) is a messaging protocol built into the default Messages app on Android phones, and it lets a verified business send branded messages with images, product carousels and tap-to-reply buttons instead of plain text. Customers install nothing and add nothing. It is the channel that gives you WhatsApp-style richness in the app the phone already ships with.

RCS lives in the phone’s built-in Messages app, so there is no app to install and no prior relationship needed, and it is governed by TRAI and carrier rules. WhatsApp is a separate app with far higher engagement among people who already use it, governed by Meta’s policies. RCS is strong for reach and for customers who do not use WhatsApp; WhatsApp is strong for sustained two-way conversation and commerce. Many businesses run both.

Apple added RCS support to iPhone from iOS 18, so RCS messages can now reach iPhones as well as Android — but carrier support and business-messaging feature availability vary, and not every rich feature behaves identically across platforms. We build every RCS campaign with SMS fallback for exactly this reason, so a handset or carrier that cannot render the rich version still receives the message.

The campaign falls back to SMS automatically, so the message still arrives — as plain text rather than a rich card. We write SMS fallback copy for every RCS template as part of the build, so the fallback reads like a deliberate message rather than a stripped-down accident with a dead link in it.

Branded sender name and logo, images and video, product carousels the customer can swipe, and suggested-reply or suggested-action buttons such as "Book now", "Track order" or "Call us". You also get delivery and read receipts, which plain SMS does not provide. The exact feature set depends on carrier support, so we confirm what is available for your audience before designing the templates.

Your brand is registered as a verified sender with the carriers, which is what puts your name, logo and a verification indicator on every message instead of an anonymous number. Nucleus Ai prepares and submits the registration along with your brand assets. Approval sits with the carriers and Google, so as with WhatsApp’s green tick we run the process properly but cannot guarantee the outcome or the date.

Yes. RCS supports delivery and read receipts, and reports button taps, so you can see what was delivered, what was opened and which suggested action people chose — per campaign and per message. That is a meaningful step up from SMS, where you get delivery confirmation but no read or engagement data.

Usually yes per message, because you are paying for a richer format and carrier-verified branding. Whether it is more expensive per result is a different question — a carousel with a working "Buy now" button generally earns more taps than a plain 160-character message. For OTPs and short transactional alerts SMS remains the sensible choice; for campaigns with something to show, RCS usually justifies the difference.

Use text SMS when the message must arrive regardless of handset, data connection or app — one-time passwords, order and delivery updates, payment confirmations, appointment reminders and service alerts. It is the only channel with effectively universal reach, and it is what customers already expect these messages to arrive on. For anything visual or conversational, a richer channel will do more.

A standard English SMS is 160 characters. Go over and the message is split into parts of 153 characters each, and you are billed per part — so a 200-character message costs two SMS, not one. Messages using non-Latin characters are limited to 70 characters per message (67 per part when split), because they are encoded differently. We write templates to land inside a whole number of parts rather than spilling one character into a second.

Yes. Messages in Devanagari, Tamil, Telugu, Bengali and other Indian scripts are sent using Unicode encoding, which every modern handset displays correctly. The trade-off is length: Unicode messages hold 70 characters instead of 160, so a regional-language message costs more per sentence. We register language-specific content templates on DLT and write to the shorter limit deliberately.

Yes. One-time passwords go out on high-priority transactional routes, which are delivered around the clock and reach numbers registered on Do Not Disturb, because they relate to something the customer is doing right now rather than to marketing. Speed and reliability matter more than anything else for OTP traffic, and we configure the routing accordingly.

Most commonly because those numbers are registered on the national Do Not Disturb list, which blocks promotional traffic by law — those recipients are scrubbed out before sending. Other causes are the message falling outside the 9am–9pm window TRAI permits for promotional content, the content not matching a registered DLT template, or the handset being switched off beyond the retry period. Delivery reports show which reason applied to each number.

Usually because the content does not match the registered DLT content template, uses variable fields inconsistently, promotes something not permitted on a transactional route, or contains a URL or sender name that has not been registered. Template registration is exact, not approximate — a message that differs from the approved wording is rejected by the operator rather than delivered. We write templates with the variable fields mapped properly the first time.

Yes, links work and clicks can be tracked using a shortened, trackable URL. There is a compliance detail: the domain used in the link generally has to be registered on the DLT platform along with the template, so links cannot be swapped in freely after approval. We register your link domain as part of setup.

Yes. We connect an HTTP API to your application, CRM, e-commerce platform or order system so the message is triggered by the event it belongs to — order placed, payment received, appointment booked, shipment dispatched — with nobody pressing send. That is how most transactional SMS should work.

Technically it is the same delivery mechanism — a pre-recorded message played to a list of numbers — but the word "robocall" usually describes unsolicited spam calls, and that is precisely what the Indian regulations exist to stop. A compliant voice broadcast goes only to numbers that have consented or are outside the Do Not Disturb registry, runs only between 9am and 9pm for promotional content, identifies the business immediately, and offers a way out. Nucleus Ai does not run campaigns to purchased lists.

Audiences that other channels underserve: feature-phone users, older customers, people who do not read comfortably in English or at all, and anyone in a setting where reading a screen is inconvenient. It is also the channel of choice for messages where tone carries meaning — a service disruption, a safety notice, a fee reminder from a school. If your customer list includes people who never reply to your SMS, voice is usually the reason to test.

Around 20 to 30 seconds for most campaigns. Long enough to state who is calling, what the message is and what to do next; short enough that people hear it to the end. If you need a keypress response, ask for it in the last five seconds and repeat the option once. We write and time the script rather than reading a paragraph aloud.

Either. You can supply a recording — an owner, a doctor, a principal, whoever carries authority with your audience — and we clean up the audio and format it for broadcast. Or we arrange professional voice-over in the languages you need. A familiar or authoritative voice usually outperforms a polished but anonymous one.

No. Voice is billed on connected call duration, so unanswered, busy and failed calls cost nothing. Retries on unanswered numbers are scheduled within the permitted window and only charged if they connect. Your report separates connected calls from attempts, so you can see both numbers.

Yes, and pairing them works well. A common pattern is a voice broadcast that explains the message and asks for a keypress, followed by an SMS to everyone who answered, carrying the link, code or reference number they need to keep. Voice delivers the message; SMS leaves the written record. We build the follow-up rules so only the right segment receives the second message.

Not for promotional content. DND-registered numbers are scrubbed out of promotional voice campaigns before dialling, and that scrubbing is not optional — TRAI penalises the business whose message was sent, not the platform that sent it. Genuine service and transactional calls tied to an existing relationship, such as a delivery confirmation or an appointment reminder the customer booked, sit outside the DND restriction and still connect.

A well-built chatbot answers common questions instantly at any hour, qualifies leads by asking the questions your sales team would ask, takes orders and payments, tracks deliveries, and hands the conversation to a person the moment it should. The measurable effect is usually fewer missed enquiries outside office hours and less time spent by staff answering the same question repeatedly.

That depends entirely on how it is built. We map your real conversations first — the actual questions, objections and buying moments — and write the bot in your tone rather than generic assistant language. It also handles English, Hindi and Hinglish, because that is how Indian customers actually type.

It hands the conversation to a human with full context, rather than looping or dead-ending. Handoff rules are part of the design: we agree in advance which intents, keywords and failure conditions should route to a person, and the customer is told plainly that someone is joining.

Yes. Automated and AI-generated responses can be incomplete, out of date or wrong, which is why our Terms state plainly that bot output is not professional advice and is never a binding quotation. We reduce the risk by scoping what the bot is allowed to answer, testing against real scenarios before launch, and routing anything sensitive — pricing commitments, medical, legal or financial questions — to a human.

Yes — that integration is usually the point. Conversations, leads and orders can sync to your CRM, spreadsheets, order management or ticketing system so nobody is copying data by hand. What is possible depends on what your systems expose; we confirm feasibility during scoping rather than after signing.

The build time depends far more on your content than on our engineering — we need your real questions, real answers, catalogue and rules before the bot can be useful. A focused bot handling a defined set of flows moves quickly; one that must cover an entire product range and integrate with an order system takes longer. We scope it in writing with milestones rather than quoting a number that ignores what you have ready.

The questions customers actually ask, in the words they actually use — screenshots of real chats are ideal — plus your answers, your catalogue or price list, your policies on delivery, returns and refunds, and the rules for when a conversation must reach a human. Most of the quality of a chatbot comes from this material, not from the model behind it.

Yes. The bot handles English, Hindi and the mixed Hinglish people actually type, including Roman-script Hindi. We test against real message samples rather than clean textbook sentences, because customers write in shorthand, with typos, and switch languages mid-sentence.

You do. The bot, its flows and its content are yours on full payment, and the conversation data belongs to you as the Data Fiduciary under the DPDP Act. Where we operate the system on your behalf we act as a processor, working only on your documented instructions.

No, and any agency that promises one is misleading you, because Google decides rankings and no third party controls its algorithms. What Nucleus Ai commits to is the process and the evidence: a technical audit, Core Web Vitals in the green, keyword-mapped content, schema markup, local search work and monthly reporting with numbers you can verify yourself in Google Search Console.

SEO is the slowest channel we sell and the only one that gets cheaper per lead the longer it runs. Early movement typically shows on long-tail, low-competition terms well before competitive head terms move, and technical fixes such as Core Web Vitals and indexing can show up faster than content-driven gains. We report from your own Search Console from month one so you can see movement rather than take our word for it.

Ads are rent and SEO is ownership. Traffic from ads stops the day the budget does; a page that ranks keeps sending customers for free, month after month. Most businesses run both — ads for this quarter, SEO for every quarter after — and the right split depends on your margin and how urgently you need volume.

AI answer engines mostly cannot execute JavaScript, so the first requirement is that your pages return real HTML rather than an empty shell that fills in after the page loads — a great many modern sites fail this without knowing. Beyond that: answer-first content that can be quoted standalone, structured data such as Organization and FAQPage, consistent business details across your site and public listings, and a robots.txt that does not block the AI crawlers. We treat this as part of technical SEO, not a separate product.

Core Web Vitals are Google’s measures of loading speed, interaction responsiveness and visual stability — LCP, INP and CLS. They are a genuine ranking input, but the larger effect is commercial: slow pages lose visitors before they read anything. We measure them on real pages rather than a lab score and fix the causes, which are usually oversized JavaScript, unoptimised images and render-blocking fonts.

Yes — Google Business Profile optimisation, categories, posts, review strategy and local citations, aimed at the map pack rather than generic national rankings. For businesses with a physical location or a service area, local search usually produces higher-intent enquiries than broad keyword work.

It changes what winning looks like rather than removing the work. Answer engines still retrieve from indexed pages, so crawlability, clean structure, fast loading and genuine expertise still decide whether you are eligible to be cited. What shifts is the payoff: a page that answers a question completely and quotably gets cited, while a page written to rank for a keyword without answering anything does not. The underlying technical work is the same investment.

No, but you do need to keep the content you have accurate. Search rewards pages that stay correct more than it rewards volume, and an out-of-date price, policy or product page actively costs you. A realistic pattern is a smaller number of pages maintained properly rather than a blog nobody updates.

They decay rather than collapse. Existing pages keep ranking for a while on accumulated authority, then slip as competitors publish, as your content ages and as search algorithms shift. Technical debt also accumulates quietly — broken links, slow pages, expired schema. SEO behaves more like maintenance than like a switch.

Impressions, average position, clicks and conversions pulled from your own Google Search Console and analytics, alongside a plain list of what we did that month and what is queued next. Because the accounts are registered in your name, you can open them and check every figure yourself — a report you cannot independently verify is a report you should not trust.

Custom-designed business sites, e-commerce and landing pages — designed from your brand rather than adapted from a theme, built mobile-first, with clean structure, schema and analytics wired in at build time rather than bolted on later. Content management is included so you can change prices, photos and posts without a developer.

It depends on what the site has to do. A content-led site that your team updates daily is often best on a CMS; a fast, highly custom marketing site or a product interface is usually better built in a modern JavaScript stack. We recommend based on who maintains the site and what it needs to do, not on what is quickest for us.

A discovery sprint that produces user flows, a technical plan and a fixed quote for the MVP; then build in weekly increments you can click and review; then launch with payments, onboarding and analytics wired in. After that the roadmap is driven by real user feedback. We deliberately scope an MVP rather than a complete product, because the first version exists to be learned from.

Timelines are fixed in the statement of work before anything starts, and they depend far more on decision speed and content readiness than on development time. The single biggest cause of slippage is waiting on copy, images, approvals or third-party access — which is why the SOW states what we need from you and when.

Yes — domain, hosting, SSL, backups and security updates can all be handled for you, and every account is registered in your name from the start. You can also host it yourself; we hand over the build and the documentation either way.

If you want us to, yes — a monthly care plan covers monitoring, backups, security updates, small changes and performance work. If you would rather your own team took it on, we hand over with documentation and a walkthrough instead. Both are genuinely available; there is no lock-in and no exit fee either way.

Pricing depends on scope and is fixed in a written statement of work before anything starts, so there are no open-ended hourly bills. Project work is billed against milestones, ongoing management is billed as a monthly retainer, and third-party costs such as Meta conversation charges, SMS credits, DLT fees, domains and hosting are passed through at cost or as quoted.

For services that require onboarding or a platform application — WhatsApp Business API and RCS in particular — yes, because that work is done up front regardless of outcome. Setup fees become non-refundable once an application has been submitted to Meta, Google or a telecom operator, which is stated plainly in our Refund Policy before you buy.

No. Retainers run month to month and either side can end them with 30 days’ written notice. There is no exit fee and no minimum term beyond what a specific project scope requires.

You do, completely. Repositories, designs, documentation, domains, hosting and analytics accounts are registered in your name and transferred to you on full payment, and that is written into the contract. Nucleus Ai does not hold client infrastructure as leverage — any competent developer can pick up the work if you leave.

Yes, within the terms published in full on our Refund & Cancellation Policy page rather than buried in a contract. In short: a full refund if you cancel in writing within 7 days of payment and before work starts; pro-rata for undelivered work after that; and if we fail to deliver what the SOW commits us to, we re-perform at our cost or refund the undelivered portion. Third-party costs already consumed cannot be recovered.

Because the honest number depends on scope, and a headline price that changes after the first call is worse than no price. What we do commit to is a fixed written quote before any work starts, third-party costs passed through at cost as separate line items, and no open-ended hourly billing. Tell us what you are trying to achieve and you get a real number, not a range.

They are charges set by someone else and passed through to you at cost: Meta’s per-conversation WhatsApp charges, operator SMS and voice rates, DLT registration fees, domain and hosting, SSL, and any paid software licences. We show them as separate lines because they are not our revenue and because they change independently of our fee. Bundling them into one number would hide which part you can actually negotiate.

We scope small first engagements rather than free trials — a single campaign, one chatbot flow, or a technical audit — so you can judge the working relationship on real output before committing to a larger build. It is quoted and paid like any other work, which is what keeps it a real piece of work rather than a sales exercise.

No — quoted fees are exclusive of GST and other applicable taxes, which are charged additionally at the prevailing rate. Invoices show the tax separately.

Where we run messaging, chatbot or analytics systems on your behalf, you are the Data Fiduciary under the Digital Personal Data Protection Act, 2023 and we act as a Data Processor — we process that data only on your documented instructions, under written terms, and we return or delete it on termination. Our Privacy Policy sets out retention periods, sub-processors and cross-border transfer handling in full.

The Digital Personal Data Protection Act, 2023 is India’s data protection law. For messaging it means you need a lawful basis — in practice, consent — before contacting someone, consent must be as easy to withdraw as to give, you must be able to evidence it, and people can ask you to access, correct or delete their data. It sits alongside, not instead of, Meta’s policies and TRAI’s DLT rules.

We notify each affected person without delay and report to the Data Protection Board of India within the timelines prescribed under the DPDP Rules, 2025, alongside any CERT-In reporting obligation that applies. Where the breach affects a system we operate for a client, we notify that client immediately so they can meet their own obligations as Data Fiduciary.

Email the address on our Responsible Disclosure Policy page with reproduction steps. We acknowledge within 3 business days, triage within 10, and offer safe harbour: good-faith research within that policy is treated as authorised, and we will not pursue or support legal action over it. We do not currently run a paid bug bounty, but we credit reporters publicly if they want it.

No. We do not sell personal data, we do not rent it, and we do not use your data or your customers’ data to train third-party AI models. Data is shared only with the platforms and infrastructure providers needed to deliver the service, under written terms, and the current sub-processor list is available on request.

This site runs no advertising or cross-site tracking. Strictly necessary storage keeps the chat assistant working and records your cookie choice; analytics loads only if you accept it, and if you decline, nothing is requested from Google at all. The Cookie Policy lists every item stored, by name.

Message us on WhatsApp or email hello@nucleusaiautomation.com with what you sell and what is not working. We will tell you honestly whether we are the right fit, and if we are, the next step is a scoping conversation that produces a written statement of work with a fixed quote before any money moves.

Accurate business information, brand assets, access to the relevant accounts, and timely decisions. The single biggest cause of delay on every project is waiting for content, approvals or third-party access — so the statement of work states exactly what we need from you and when.

Yes, frequently. We can take a defined scope — messaging infrastructure or technical SEO, for example — while another team handles design, ads or content. What matters is a clear boundary of responsibility so nothing falls between two suppliers.

Support terms are set in your agreement rather than left vague. Ongoing engagements include an agreed response and resolution approach; project engagements can convert to a monthly care plan or a clean handover with documentation. Either way you keep the accounts and the code.

Write to our Grievance Officer using the contact details on our Terms & Conditions page. We acknowledge complaints within 24 hours and resolve them within 15 days, as required by the Consumer Protection (E-Commerce) Rules, 2020. If you are not satisfied you retain your rights under the Consumer Protection Act, 2019 and, for data matters, before the Data Protection Board of India.

A named point of contact for the engagement, not a ticket queue. Day-to-day communication happens on WhatsApp because that is the channel we sell and the one that gets answered; anything contractual — scope, quotes, sign-off, changes — goes in writing by email so there is a record both sides can point to later.

That is a normal starting point and usually cheaper to fix than to rebuild. We audit what exists, tell you plainly what is worth keeping and what is costing you, and quote the fix separately from any new work. We will say when a rebuild genuinely is the cheaper answer, and we will say when it is not.

The chat assistant on this site answers instantly at any hour. A person replies within business hours, and engagements with a support SLA have their response times written into the statement of work rather than implied. We would rather commit to a number in writing than advertise "24/7" and miss it.

Yes, and confidentiality already binds us with or without one — our standard Terms & Conditions include mutual confidentiality obligations that survive the engagement by three years. If your organisation requires its own NDA, send it across and we will review and sign it.

We do not buy links, guarantee rankings, send messages without documented consent, or run campaigns for products and claims that platform policy or Indian law prohibits. We also decline work where the honest answer is that the client does not need it — a business with no conversation volume does not need a chatbot, and saying so costs us one sale and saves the relationship.