Tell us what you’re building.

What this page is for

This is the front door for six kinds of conversation: a pricing question, a free audit request, a security review, an existing-customer support issue, a partnership or reseller enquiry, and a general question that does not fit anywhere else. The intent dropdown exists so that the first routing decision is made by you rather than by someone guessing from a subject line at nine in the morning.

A useful first message is specific about scale and constraint. Tell us how many contacts you hold, which channels you actually use today, what you are paying for them and by when you need a decision. If the problem is a workflow rather than a platform, describe the handoff that keeps breaking, not the tool you think you need. The more concrete the first message, the less of the first call is spent establishing basics.

Please do not send passwords, API keys, card numbers or unredacted customer records through the form or by email. If a security review needs a sample export, we will agree a redaction method first. The form is a first contact channel, not a secure file transfer system, and treating it as one is how avoidable incidents begin.

How quickly you will hear back

A standard enquiry gets a reply within one business day. Enterprise and security reviews target four business hours, because those conversations usually have a procurement calendar behind them and a slow first reply costs the buyer a week. Existing Scale customers have round-the-clock cover with a one-hour target and a named technical account manager, and Enterprise adds a customer success manager and a phone route.

Targets are expressed in business hours rather than wall-clock hours, so a message sent on Friday evening is not expected to be answered on Saturday. We do not publish desk hours, because the team answers when the queue is live rather than behind a switchboard, and inventing a nine-to-six window would be a promise the operation cannot keep on a launch week.

If something is genuinely on fire, say so in the subject line and include the workspace name. A failed send on a live campaign is triaged ahead of a question about annual billing. The same applies to a suspected security issue: write to security@loopnow.in, which is monitored separately and acknowledged within one business day even when the sales queue is deep.

Formal grievances follow a separate clock. Write to info@loopnow.in, addressed to the grievance officer, Mayur Chaturvedi, and we acknowledge within 48 hours and aim to resolve within one month, which sits inside the 90-day window the DPDP framework expects once its substantive duties commence. If a rights request cannot be resolved with you directly, the notice explains how to escalate to the Data Protection Board.

What happens after you press send

The browser checks the required fields before the request leaves the page, then posts the form to the contact endpoint. A hidden field sits where a person will not see it; if a bot fills it, the endpoint returns a success response and stores nothing. That deliberate silence is better than an error message that teaches a scraper which field to avoid next time.

Server side, the name is checked for a length between two and one hundred characters, and the email is checked against a simple pattern and a two hundred character ceiling. Submissions are then counted against a salted hash of the client address, with a limit of five per minute. Exceeding it returns a rate error rather than a queue, which is enough to stop a naive flood without punishing a person who pressed send twice.

A valid submission is written to the site database with a timestamp, then the browser is redirected to a confirmation view. Failures come back as named codes such as invalid-name, invalid-email, rate or unavailable, and the page shows the code in plain language with the email address as a fallback. Nothing about the failure is hidden behind a generic apology.

Exactly what the form stores

Six things are written to the database when you submit: your name, your work email in both its original and normalised form, your company, an optional phone number if you type one, the intent you selected, and your message. Alongside those sit the path you arrived from, the consent version and the moment consent was given, and a salted hash of the client address used for rate limiting.

The raw IP address is not stored. It is salted and hashed before the write, so the database can tell that two submissions came from the same place within a minute without keeping an identifier that could be reversed later. There is no advertising pixel on this page, no session recording, and no third-party form service holding a parallel copy of your message.

Phone is optional and absent unless you provide it, which matters because the visible form does not ask for one. The intent field defaults to general if nothing is selected, and the message is trimmed to five thousand characters. If you leave the message blank the enquiry is still valid, though a blank message usually turns the first reply into a request for context.

What consent covers, and what it does not

The checkbox is required, and ticking it records the notice version in force on the day, which is currently dated 4 November 2026. That pair, version and timestamp, is what makes the consent auditable later. A consent record without a notice version proves that somebody clicked something, not what they were shown when they clicked it.

What you are agreeing to is a reply about LoopNow: an answer to your question, a call if you want one, and follow-up on the specific thing you raised. You are not agreeing to join a newsletter, a product-update list or an outbound sequence. The contact record and the marketing list are separate objects on purpose, and a sales enquiry does not silently enrol you in a monthly digest.

You can withdraw consent at any time by writing to info@loopnow.in with the address you used. Withdrawal stops future contact and future processing for that purpose. It does not retroactively make earlier processing unlawful, and it does not delete records we must keep as evidence that the earlier processing was permitted. Those two ideas are often conflated, and separating them makes the request easier to answer.

How long an enquiry is kept

An enquiry is kept while the conversation is live and for as long as it takes to answer it, then removed under the retention schedule published in the privacy policy rather than left in a table indefinitely. Deletion requests are logged, so the removal itself is evidence. The privacy policy states the categories; the sweep is what makes the statement true.

We do not publish one number for every enquiry, because the clock depends on what the message becomes. A pricing question that ends in one reply has a shorter life than a security review that becomes a contract, and a contract carries statutory retention of its own. What is consistent is the mechanism: a documented schedule, applied by a job, with a log that can be produced on request.

Two categories outlive the rest. Consent records are retained as evidence of lawful processing, and billing records are retained for the period tax law requires. Both are narrow exceptions with a stated reason. If you need to know the current schedule for your own record, info@loopnow.in will confirm it in writing rather than pointing at a paragraph that has to cover every case.

Asking for a copy, a correction or deletion

Write to info@loopnow.in from the address you used, or state that address in the message if you are writing from another one. We verify identity before acting, usually by replying to the address on record and asking for a confirmation. Verification is not obstruction; it is the control that stops somebody else from deleting your enquiry history.

An access request returns what we hold: the enquiry row, any chat lead created by the site assistant, and the consent record. A correction fixes a misspelt name or a stale company. An erasure removes the message body, name, company and email from the live table, and propagates to derived copies rather than stopping at the first one. Consent evidence stays, and you are told that it stays and why.

The Act also provides for a nomination, so that another person can exercise your rights if you die or become incapacitated. That request follows the same channel and the same verification. If an answer does not satisfy you, ask for escalation to the grievance route; if it still does not, the Act provides for a complaint to the Data Protection Board of India. This page describes the process, not the law, and it is not legal advice.

The free audit, in detail

The audit is a forty-five minute working session, not a slide deck. We map one workflow end to end, name the data it needs, specify the agent that would run it, write the guardrails and produce an indicative rupee cost including GST. The written roadmap follows within two working days, and it is yours to keep whether or not you buy anything.

Bring one workflow, the volume it handles in a normal week, the systems it touches and the constraint that matters most, whether that is cost, accuracy, language or a compliance rule. Redacted sample data helps more than a description. If the workflow depends on a system we cannot reach, say so early, because the honest answer may be that the audit should focus on a different process.

The audit is not a disguised scoping call and it is not a commitment. We sometimes conclude that a workflow should stay manual, or that the volume does not justify an agent yet. Saying that in a written document is more useful than selling a pilot that fails in month two, and it is the reason the roadmap includes a section on what we would not automate.

Trials, plans and procurement

Three entry points exist. The free plan needs no card and carries 1,000 contacts, 5,000 emails, 100 voice minutes and 250 WhatsApp messages. The fourteen-day Growth trial opens 25,000 contacts, 1,00,000 emails, 1,500 voice minutes and the full workflow builder, and cancels with one click. Paid plans start at ₹2,999 a month for Starter and ₹7,999 for Growth, before 18% GST.

Procurement usually needs four things: a GSTIN invoice, a purchase order reference, a signed DPA and a vendor form. All four are routine. Enterprise adds a private VPC, custom models, SSO and a named customer success manager, and it is quoted from ₹75,000 a month rather than listed as a number, because a private deployment is scoped rather than ordered from a menu.

There is no discount theatre. Annual billing takes roughly twenty percent off and locks the rate for twelve months, and that is the published lever. If a budget genuinely cannot meet a plan, the better conversation is about starting on a smaller plan and growing, not about a temporary price that reappears at renewal and sours the second year.

Security reviews and questionnaires

Ask for the security pack through the form with the security intent, or write to security@loopnow.in directly. The pack contains the sub-processor list with purpose and region, the data processing agreement, the current status of each control and a plain statement of what is certified and what is not. Reading it before the first call turns a two-week exchange into a single meeting.

We can answer questions about residency, access control, retention, erasure propagation, breach handling and the consent model without inventing anything. Primary storage and processing are in AWS Mumbai. Cloudflare terminates edge requests, Razorpay handles payments, Postmark provides transactional fallback and Datadog provides observability, and all three operate outside India under the DPA.

What we cannot provide is a SOC 2 Type II report, because none exists, or an ISO 27001 certificate, because the audit is in progress with a target of the third quarter of 2027. A questionnaire that requires either will get an honest no in the relevant row. Buyers who need a certificate this quarter should know that before they spend time on an evaluation, which is why the status is published rather than revealed late.

If the form fails, or you would rather write directly

A rate error means five submissions arrived from the same connection inside a minute; wait a minute and try once. An unavailable error means the database write failed, which is our problem rather than yours, and email is the correct fallback. Invalid-name and invalid-email point at the field named in the message, and neither is a judgement about you.

The form is plain HTML and posts without JavaScript, so it works with a keyboard, a screen reader and a text browser. Labels are associated with inputs, the honeypot is hidden from assistive technology, and the confirmation page is a normal URL that can be bookmarked. If any part of it is hard to use, write to info@loopnow.in and describe the barrier; accessibility fixes are easier to make when the report names the step.

There is no published phone number and no walk-in office. The Bhayandar West address in Mumbai is the registered correspondence address for LoopNow Technologies Pvt. Ltd., and post sent there reaches the company, but nobody will be at a reception desk to take a meeting. Email is the reliable channel, and it is monitored by people who can act on what arrives.

What we will not do with your message

Your message is not sold, rented, enriched with third-party data or fed into a shared model. It is read by the people who answer it and stored so that the next person who picks up the thread has context. We do not run an outbound sequence against enquiries, and we do not add a sales contact to a newsletter without a separate, explicit opt-in.

Nobody will call from an unknown number because you downloaded a page, and no WhatsApp message will arrive from a number you have never seen. If a partner or reseller is going to be involved in your enquiry, we ask first. Those rules are unglamorous, but they are the difference between a contact form and a lead-generation machine with a privacy policy bolted on.

The assistant on this site is labelled as an assistant. It answers from published pages, it does not claim to be a person, and it escalates to email when a question needs one. Conversations with it may create a chat lead so that a follow-up is possible, and that record follows the same access and erasure rules as the form. The label is not decoration; it is how you decide whether to use it.