The mailbox exists and accepts mail
The domain has mail servers and the server confirmed this address during the handshake.
Turn a list of names and companies into work emails and phone numbers your team can use.
Upload a spreadsheet or enrich one profile at a time. Each contact is looked up across several data providers in turn, checked, screened against your opt-out list and sent to your CRM. Credits are spent on contacts revealed, not on searches.*
Data enrichment takes a record you already have, usually a name and a company, and adds the fields you are missing: a work email, a phone number, a job title, the company's size and industry. It also replaces values that have gone out of date.
Add the fields a form, event list or CRM import never captured, so reps can actually reach the person.
Replace an email that now bounces or a title that changed, and mark people who have moved company.
Add company context such as size band, industry and location, so leads can be scored, routed and prioritised.
People change jobs, and a work email usually stops working when they leave. Titles change with promotions. Companies merge, rebrand and move domains. Direct lines are reassigned.
We do not quote an annual "B2B data decay" percentage. The figures that circulate online could not be traced to a primary source we could verify. To measure your own decay, re-check a sample of 200 records older than 12 months and count bounces and job moves.
Illustrative record. Names and values are invented for the example.
Person fields tell you who to contact and how. Company fields tell you whether the account is worth contacting at all. Some go stale fast, so re-check them before you rely on them.
| Field | Example | What it is used for | Goes stale | Credits |
|---|---|---|---|---|
| PersonWork email | [email protected] | Email sequences; the main key for matching and deduplicating CRM records | Fast ends with the job | 1 |
| PersonMobile / direct dial | +91 98•• ••210 | Calls and, where consent exists, WhatsApp follow-up. TRAI rules apply to promotional calls | Slow mobile · Fast desk line | 5 |
| PersonJob title | Head of Purchase | Personalising the message; checking the persona fits | Fast | With profile* |
| PersonSeniority | Head · Director · Manager | Routing to an account executive or an SDR; tiering for ABM | Medium | With profile* |
| PersonDepartment | Procurement | Choosing which message and case study to send | Medium | With profile* |
| PersonLinkedIn URL | linkedin.com/in/… | A stable ID for deduplication; research before outreach | Slow | With profile* |
| PersonLocation | Pune, MH, IN | Territory assignment, call-time windows, and which privacy law applies | Medium | With profile* |
| CompanyDomain | acmepumps.in | The company key: links people to accounts and finds email patterns | Slow | With profile* |
| CompanyIndustry | Industrial machinery | Segmenting campaigns; checking ideal-customer fit | Slow | With profile* |
| CompanySize band | 201–500 employees | Lead scoring; matching the right plan or offer | Medium | With profile* |
| CompanyRevenue band | ₹100–500 Cr | Account tiering. Bands for private companies are estimates, so treat them as a guide | Medium | With profile* |
| CompanyHQ location | Pune, IN | Territories, GST state, and data-residency questions in the deal | Slow | With profile* |
| CompanyTechnographics | Uses Microsoft 365 · a CRM | Choosing which product to pitch; replacement and add-on campaigns | Medium | Confirm* |
| CompanyFunding | Last round · date | Timing outreach after a raise, when budgets open up | Medium | Confirm* |
| CompanyHiring signals | 8 open sales roles | A growth signal: teams that are hiring need tools and onboarding | Fast | Confirm* |
Credits: 1 per work email revealed, 5 per phone revealed. Profile and company fields come back with the record where the providers hold them*. Whether technographics, funding and hiring signals are available on your plan: confirm with XcellHost*. "Goes stale" is a qualitative guide, not a measured rate.
The same pipeline runs whether you enrich one profile or a 1,000-row file. Nothing reaches your CRM until it has been checked and screened.
Upload a CSV, pick a saved search, or open a profile in the browser extension and click enrich. Name plus company or domain is enough to start.
CSV · extension · APIThe contact is sent to one data provider, then the next, until a usable email or phone comes back. Providers that miss cost you nothing.*
Several providers · confirm list*Emails go through syntax, domain and mailbox checks, with extra handling for catch-all domains. Phones are matched against the person's name where the data allows.
Valid · risky · invalidContacts on your opt-out list are dropped. The rest go to your CRM, a spreadsheet export or your own system over API, with source and date kept on each record.
CRM · CSV · webhookNo single data provider holds everyone. A waterfall sends each contact to several providers in a fixed order and stops as soon as one returns a usable result. Pick a scenario to watch one contact go through it.
Clean the name, resolve the company to its domain, and skip the contact if it is on your opt-out list.
The provider most likely to hold this kind of contact goes first. The order can differ by country or field.*
A miss moves the contact down the list. A miss costs you nothing.*
Later providers are not queried, which keeps cost and response time down.
The email gets syntax, domain, mailbox and catch-all checks. The phone gets a line-type check and, where possible, an ownership check.
The opt-out list is applied again, then the record goes out with its source and the date it was checked.
| Question | One data provider | Waterfall across several |
|---|---|---|
| Who can be found | Only people that one provider holds. Coverage gaps by country or sector stay as gaps | Gaps at one provider can be filled by another, so more of the list usually comes back |
| Freshness | Tied to one provider's refresh cycle | Every result is checked at the time of delivery, whichever provider supplied it |
| Paying for misses | Often charged per search, found or not | Charged on reveal; misses are free* |
| Dependence on a vendor | If the provider changes terms or quality, everything changes with it | The provider order can be changed without changing your workflow |
| Speed | One call, so faster | Slower when the match comes late in the order; bulk jobs run in the background |
| Privacy due diligence | One sub-processor to review | More sub-processors to review. Ask for the list and the DPA terms (see the buyer's guide) |
A qualitative comparison. We do not publish provider counts, coverage or accuracy figures; test a sample of your own list instead.*
A found email is not the same as a deliverable one. Each email comes back with a status, and each phone with a line type. Use them to decide what goes into a sequence or a dialler.
The domain has mail servers and the server confirmed this address during the handshake.
The server says yes to any address at the domain, so this mailbox cannot be confirmed. Many corporate domains are set up this way.
The server timed out or deferred the check, or the address is a role inbox (sales@, info@) or a disposable one.
The mailbox or domain does not exist, or the address is malformed. Hard bounces damage your sender reputation.
Status names vary between tools. Whether catch-all and risky results use credits: confirm with XcellHost*.
| Type | Who it reaches | Changes when | Best for | Watch out |
|---|---|---|---|---|
| Mobile | The person, directly | Rarely. Numbers usually follow the person across jobs | Senior decision-makers and owner-led businesses | Personal data in full; DND preferences and TRAI rules apply to promotional calls |
| Direct dial | The person's desk line | They change desk or employer | Large offices with direct lines | Goes stale with job changes; re-check before a calling campaign |
| Switchboard | Reception or the main company line | The company moves or changes its number | Confirming someone works there, and being routed through | Lowest connect rate to the actual person |
| VoIP / virtual | A cloud number that may forward anywhere | It can be reassigned at any time | Start-ups and remote teams | Check ownership more carefully before you rely on it |
Indian subscribers record their call and SMS preferences in the National Customer Preference Register, through 1909 or the TRAI DND app, and can block promotional calls by sector. A B2B purpose does not change this, because the rules follow the number.
Choose the input that fits how the work arrives: a file from an event, one profile a rep is looking at, or a form submission your systems should enrich without anyone clicking.
Upload a CSV, match its columns to the fields, choose email, phone or both, and run it. The output file keeps your columns and adds the new fields, a status for each one and the date it was checked.
Search by name and company, or paste a profile URL, and reveal only the fields you need. Useful before a call when you need one number now rather than a whole list.
The browser extension adds an enrich button to supported profile pages. One click finds the contact details and saves the person to a list, without copying anything into a spreadsheet.
Connect the CRM and choose which records to enrich: new leads, records with missing fields, or records not checked for a set number of days. Results are written back to the fields you map.
Send a person, get back the enriched record. Bulk jobs return a job ID and post results to your webhook when they finish. The example below shows the shape of a typical exchange.
POST https://api.xcellenrich.example/v1/enrich
Authorization: Bearer <YOUR_API_KEY>
Content-Type: application/json
{
"first_name": "Priya",
"last_name": "Mehta",
"company_domain": "acmepumps.in",
"linkedin_url": null,
"fields": ["work_email", "phone"],
"external_id": "lead_10482",
"webhook_url": "https://crm.yourco.example/hooks/enrich"
}Placeholder endpoint. The .example domain is reserved and does not resolve. The real base URL, authentication and field names are confirmed at onboarding*.
{
"request_id": "enr_7f3c21",
"status": "completed",
"person": {
"full_name": "Priya Mehta",
"title": "Head of Purchase",
"seniority": "head",
"department": "procurement",
"location": "Pune, IN"
},
"work_email": {
"value": "[email protected]",
"status": "valid",
"checked_at": "2026-11-17T10:42:05+05:30",
"credits": 1
},
"phone": {
"value": "+9198XXXXX210",
"line_type": "mobile",
"credits": 5
},
"company": {
"domain": "acmepumps.in",
"industry": "Industrial machinery",
"size_band": "201-500"
},
"suppressed": false,
"source_log": [
{"step": 1, "result": "miss"},
{"step": 2, "result": "match"}
],
"credits_used": 6
}Background lead campaigns and bulk jobs post each finished record, or a finished-job notice, to a URL you choose. Your system writes it to the CRM, notifies the owner, or adds the person to a sequence.
external_id to update the right record, never to create duplicates{
"event": "enrichment.completed",
"job_id": "job_51ac09",
"external_id": "lead_10482",
"work_email": {"value": "[email protected]", "status": "valid"},
"phone": {"value": "+9198XXXXX210", "line_type": "mobile"},
"suppressed": false,
"credits_used": 6,
"sent_at": "2026-11-17T10:42:07+05:30"
}| Enriched field | Typical CRM field | Zoho CRM · Leads (API name) | Rule of thumb |
|---|---|---|---|
work_email | Email | Write only when the status is valid. Keep catch-all addresses in a separate field | |
phone · mobile | Mobile | Mobile | Keep the line type. Check DND before any promotional call |
phone · direct / switchboard | Phone | Phone | Do not overwrite a number a rep has confirmed |
title | Job title | Designation | Map seniority and department to picklists for reporting |
company_domain | Website | Website | Store the bare domain; it is your account-matching key |
industry | Industry | Industry | A picklist, so map the provider's values to yours |
size_band | Employees | No_of_Employees | A number field: store the band in a custom picklist instead of guessing a number |
location | City · State · Country | City · State · Country | Use one country format everywhere (ISO codes are easiest) |
linkedin_url | Custom | Custom field | A useful secondary key for deduplication |
status · checked_at · source | Custom | Custom fields | Needed to show where and when you got the data (DPDP, GDPR Article 14) |
Zoho field names are the standard Leads-module API names as we understand them in Nov 2026; check your own layout, as admins can rename and add fields. We help with Zoho apps such as Zoho Assist and Zoho WorkDrive. CRM field-mapping setup is in the configurator.
Built for sales and marketing teams who need fewer bounced emails and fewer wrong numbers, with a record of where each contact came from.
Drop in a CSV, map the columns, and watch rows fill in. Download the result with a status column for every field.
Filter people by role, department and location; save the search and come back to it.
Enrich a profile you are viewing and save it to a list in one click.
Syntax, domain and mailbox checks, with catch-all domains flagged separately so you can decide.
Where providers allow, the number is matched to the person's name before it is shown.
Set an audience filter once; new matches are found on a schedule and sent by email or webhook.
Managers and agents, shared or per-user credit pools, lists and tags for the team.
Upload your do-not-contact list; matching people are never revealed or exported again.*
Credits by user and list, find rates by field, and a log of who exported what.
Pick a team to see the workflow we usually set up, the fields it depends on, and the mistake to avoid.
Reps build an account list, pick two or three roles per account, enrich them and push only checked contacts into sequences. Phones are revealed only for top-tier accounts, because they cost five times as much.
Avoid: loading catch-all addresses into a high-volume first touch. One bad batch can push your spam and bounce rates up for the whole domain.
Ask for a work email only and enrich the rest: company, size, industry, title. Score and route on the enriched fields, so sales gets the right lead and nurture gets the rest.
Avoid: a privacy notice that says nothing about enrichment. If you add data from other sources, say so where you collect the email (DPDP section 5; GDPR Articles 13 and 14).
Re-check old contacts on a schedule, find people who have moved company, merge duplicates and stop emailing addresses that now bounce. Report bounce rates before and after.
Avoid: letting enrichment overwrite values a rep has corrected by hand. Set write-back rules first.
Recruiters enrich shortlisted profiles and reach out once, with a clear note on where the details came from and how to opt out. If the candidate is not interested, the data is deleted.
Avoid: keeping candidate data "just in case". Set a retention date for every list.
For a short list of high-value accounts, find everyone who influences the decision: the budget holder, the champion, the technical evaluator, procurement. Then coordinate email, calls and ads to the same group.
Avoid: enriching whole companies. Reveal only the roles in the buying group to keep both cost and data volume down.
Channel teams recruiting partners by region need the founder or sales head, not a general inbox. Enrich by company and city, then hand over to the partner programme.
Avoid: treating an owner's mobile as "business data". It is personal data, and the TRAI rules apply to promotional calls to it.
Registrations and badge scans often arrive with a name and company only. Enrich the missing work email, check it, and send follow-ups split by who attended, who visited the stand and who registered but did not come.
Avoid: follow-up the registration notice did not mention. Say at sign-up that you will follow up and may add business details.
Specific connectors depend on your CRM and plan; we confirm the list for your stack before you buy.*
Field mapping for each destination is shown in Inputs & API. We also supply Zoho apps such as Zoho Assist and Zoho WorkDrive. For WhatsApp follow-up after consent, ask about our messaging partners*.
Four habits keep a contact database clean, plus the sending rules the big mailbox providers now enforce. Do these and your bounce and spam numbers stay where they should be.
Merge duplicates before you enrich, so you do not pay for the same person twice.
One format per field makes matching, routing and reporting work.
+919812345210acmepumps.in, not https://www.…A suggested schedule. Tune it to your own bounce data.
Mailbox providers publish a spam-complaint limit, not a bounce limit. So set your own stop rule for bounces.
| Requirement | Gmail · all senders | Gmail · 5,000+ a day | Yahoo · bulk senders |
|---|---|---|---|
| Authentication | SPF or DKIM | SPF, DKIM and DMARC | SPF and DKIM; DMARC must pass |
| DMARC policy | — | At least p=none; From domain aligned with SPF or DKIM | At least p=none; relaxed alignment accepted |
| Unsubscribe | — | One-click for marketing mail, plus a visible link in the body | One-click (RFC 8058) plus a visible link; honour within 2 days |
| Spam-complaint rate | Below 0.3% (advice: below 0.1%) | Below 0.3% (advice: below 0.1%) | Below 0.3% |
| Transport, DNS & keys | TLS; valid forward and reverse DNS; DKIM key of 1024 bits or more | TLS; valid forward and reverse DNS; DKIM key of 1024 bits or more | DKIM key of at least 1024 bits recommended |
| In force since | 1 Feb 2024 | 1 Feb 2024 | Feb 2024, phased in over the first half of 2024 |
Sources, read 17 Nov 2026: Gmail Help, "Email sender guidelines"; Yahoo Sender Hub, "Sender best practices". Rules change, so check both before a large send.
Prices are billed annually. USD shown at ₹95.17 per US$ (rate of 26 Oct 2026, as on our GitHub page). Indicative · excl. 18% GST — confirm with XcellHost.
Plan limits and credit costs follow the published plan sheet we mirror, read on 17 Nov 2026 (in INR; the vendor's own pricing page could not be loaded). Monthly billing is offered by the platform but no monthly price is published, so we quote it. Unused-credit rollover: confirm with XcellHost*. Indicative — confirm with XcellHost.
The same figures as the plan cards above, in one table. Indicative · excl. 18% GST — confirm with XcellHost.
| Feature | Free | Starter | Growth | Scale |
|---|---|---|---|---|
| Price | ||||
| Per month, billed annually | ₹0 | ₹1,875 | ₹3,600 | Custom |
| Per year | ₹0 | ₹22,500 | ₹43,200 | Quoted |
| US$ equivalent (₹95.17) | US$0 | ≈ US$19.70/mo | ≈ US$37.83/mo | INR or USD quote |
| Cost per credit if all are used | — | ₹7.50 | ₹6.00 | Quoted |
| Credits & seats | ||||
| Credits | 30 to try | 3,000 a year | 7,200 a year | 10,000+ a year |
| Credit allocation | — | Shared pool | Per user | To suit |
| Seats | 1 | 3 · 1 manager + 2 agents | 5 · 2 managers + 3 agents | To suit |
| Work email reveal | 1 credit on every plan | |||
| Phone reveal | 5 credits on every plan | |||
| Bulk & automation | ||||
| CSV enrichment | — | 100 rows × 5 uploads | 500 rows × 10 uploads | 1,000 rows × 100 uploads |
| Bulk view | 5 contacts | 20 | 50 | Confirm* |
| Background lead campaigns | — | 3 · hourly or daily | 5 · every minute, hourly or daily | Up to 500 |
| Leads per campaign filter | — | 100 | 300 | 1,000 |
| Lists · tags | 2 · 2 | 10 · 5 | 20 · 10 | 100 · 50 |
| Tools & support | ||||
| Email and phone checks | ✓ | ✓ | ✓ | ✓ |
| Browser extension | ✓ | Confirm* | Confirm* | Confirm* |
| AI recommendations | — | ✓ | Confirm* | Confirm* |
| Reports | — | Confirm* | Detailed performance | Confirm* |
| Support | Community | Priority email and chat | Dedicated account manager | |
| Service-level agreement | — | — | — | ✓ |
"Confirm*" means the published plan sheet does not state it for that tier. "Cost per credit" is the annual price divided by the year's credits; it rises if credits go unused. Monthly billing, rollover and Scale pricing are quoted.
Credits depend on how many contacts you send, how often an email or phone is found (your hit rate), and how many contacts need a phone at all. A phone costs five times an email, so it usually decides the plan.
Starter. 600 is 20% of its 3,000 credits, so five lists like this fit in a year.
Starter, using 53% of the year's credits. A second list like it would need Growth.
Growth, using 96% of its 7,200 credits. Any growth in volume means Scale.
Hit rates in the examples are assumptions to show the arithmetic, not XcellEnrich results. Your real rates depend on the country, sector and seniority of the list, so test a sample first.
Assumes misses cost nothing* and every found email and phone is revealed. Cost per find is the plan price divided by the credits you would use (capped at the plan's credits), excl. GST. Indicative — confirm with XcellHost.
Annual plans are billed in INR on a GST invoice. Setup services are delivered by XcellHost engineers.
Both run in your browser. Your find rates and costs are assumptions you set; change them to match your own lists.
Emails 1 credit, phones 5 credits, charged only when found (assumed*). Growth credits are allocated per user — confirm pooling with XcellHost*.
Assumes about 1 minute per contact to review an enriched record. Illustrative only; excl. GST.
A work email or mobile number identifies a person. These are the rules that usually apply to B2B prospecting from India, and what each means in practice. A summary, not legal advice: confirm your position with counsel.
The Act covers digital personal data, including work contact details. Section 3(c) lists what it does not cover. Clause (ii) is the one enrichment users ask about:
"(ii) personal data that is made or caused to be made publicly available by—
(A) the Data Principal to whom such personal data relates; or
(B) any other person who is under an obligation under any law for the time being in force in India to make such personal data publicly available."
What it means for enrichment. The exclusion turns on who made the data public. Contact details that providers have compiled, inferred or bought were usually not published by the person, so plan as if the Act applies. Keep a source on every record so you can show where the data came from.
B2B outreach can rely on legitimate interest (Article 6(1)(f)) if it passes a three-part test: a real purpose, processing that is necessary for it, and a balance that does not override the person's interests. Recital 47 accepts that direct marketing may be a legitimate interest.
When data does not come from the person, Article 14 requires you to tell them who you are, your purpose and legal basis, their rights and the source of the data. You must do this within a month, or at the latest in your first message if you use the data to contact them. An objection to direct marketing (Article 21) must always be honoured. National e-marketing laws may still require consent for email.
The rules follow the phone number, so they apply to B2B calls and SMS too.
Applies to commercial email, B2B included. There is no consent requirement, but every message must:
You remain responsible if an agency or tool sends for you.
| Rule | Channel | What it requires |
|---|---|---|
| Yahoo bulk-sender rules | Honour unsubscribes within 2 days; one-click unsubscribe | |
| Gmail bulk-sender rules | One-click unsubscribe plus a visible link, for 5,000+ messages a day | |
| CAN-SPAM | Email to US recipients | Honour within 10 business days |
| TRAI TCCCPR (2025) | Calls and SMS in India | No new consent request for 90 days after an opt-out |
| GDPR Article 21 | Any direct marketing to EU/UK people | Stop on objection; no balancing test |
| DPDP section 6(4) | Any processing based on consent | Withdrawal as easy as giving consent; then stop |
Practical rule: process every opt-out within 2 days, across every channel, and keep the opt-out record itself so the person is never re-enriched or re-imported.
Keep enriched contacts only while the purpose lasts. Give every list a review date, delete records that never engaged, and erase on withdrawal or request (DPDP section 8(7)). Keep the suppression record: it is what stops the person being added again.
XcellEnrich is a partner platform supplied and supported by XcellHost. Data processing location — confirm with XcellHost*. If records must stay in India, we can sync enriched data into a CRM or database in our Mumbai Tier IV data centre.
Ticks stay in this browser only. Need help? Our virtual DPO (from ₹19,999/mo*) and DPDP compliance platform (from ₹14,999/mo*) cover notices, consent and rights requests.
Sources, read 17 Nov 2026: Digital Personal Data Protection Act 2023, ss. 3, 5–8, 11–14 and Schedule; DPDP Rules 2025, G.S.R. 846(E), 13 Nov 2025 (phasing as summarised by S.S. Rana & Co., 14 Nov 2025); TRAI press releases 11/2025 (12 Feb 2025) and 91/2026 (10 Jul 2026); GDPR Arts 6, 14, 21 and Recital 47; FTC, CAN-SPAM Act: A Compliance Guide for Business; Gmail Help, "Email sender guidelines"; Yahoo Sender Hub, "Sender best practices".
Demo results on a vendor's own sample tell you little. These questions show how the data is sourced, checked, charged for and protected. Ask for the answers in writing.
Ask XcellHost too. We answer each one in writing with your quote, including the points marked "confirm*" on this page.
No term matches. Try a shorter word.
Estimate email and phone reveal volumes and compare plans before choosing your subscription.
Discuss CRM field mapping, API integration and team onboarding with our team.
Plan opt-out handling, retention and access controls alongside your enrichment workflow.
For each person: a work email and, where one is available, a phone number, plus title, seniority, department, location and company details. Each email has a status (valid, catch-all, risky or invalid) and a check date, and each phone has a line type.
A revealed work email costs 1 credit and a revealed phone number 5 credits. Paid plans grant the year's credits up front: 3,000 on Starter (₹22,500 a year) and 7,200 on Growth (₹43,200 a year). Not-found results should not use credits*. We confirm this, and rollover, in your quote.
Each contact is sent to one data provider after another until one returns a usable result. Because no single provider holds everyone, this usually fills more of a list than one source alone. The trade-offs are speed, when a match comes late in the order, and more sub-processors to review.
A catch-all domain accepts mail for any address, so the specific mailbox cannot be confirmed. Send to these in small batches, watch your bounces, and keep them out of high-volume first touches.
Several providers are queried in sequence. We do not publish provider counts, coverage or accuracy figures that are not our own. Ask for a test on a sample of your list, ideally one where you already know the right answers, and judge the find and bounce rates yourself.*
Only annual-billed prices are published, so monthly billing is quoted on request. USD figures are conversions at ₹95.17 per US$ (26 Oct 2026). All prices are indicative and exclude 18% GST. Upgrades mid-term are pro-rated.
Only lawfully. The DPDP Act's exclusion for public data covers only data the person made public themselves, or that someone was legally required to publish, so plan for notice and consent. Promotional calls must come from 140-series numbers, respect DND preferences and follow TRAI's TCCCPR. This is not legal advice.
You keep one suppression list across email, phone and messaging. Anyone on it is skipped during enrichment and removed from exports. We suggest processing opt-outs within 2 days, the strictest common deadline (Yahoo). TRAI bars asking again for 90 days after a call or SMS opt-out.
Re-verify emails before each new sequence, re-check records untouched for six months every quarter, and re-check or delete records older than 12 months that never engaged. Adjust the schedule to your own bounce data.
Yes. There is a REST API with webhooks, CSV import and export, and connectors for CRMs and no-code automation tools. The API example on this page uses a placeholder endpoint. Tell us your CRM and we will confirm the connector and field mapping before you buy.*
XcellEnrich is a partner platform supplied and supported by XcellHost. Data processing location — confirm with XcellHost*. If records must stay in India, we can sync enriched data into a CRM or database hosted in our Mumbai Tier IV data centre.
Yes. The Free plan gives 30 credits and one seat with no card, enough for about 30 emails or 6 phone numbers. For help, call +91 22 6711 1555, WhatsApp +91 86570 32540 or email [email protected]. Our NOC and SOC run 24×7 from Mumbai.
Please don't attach or paste personal data here. We'll send a secure upload link for the sample.