Service Delivery Policy
Last updated: 8 September 2026
Nexon Enterprise provides digital services. There is no physical product and nothing is shipped. This policy explains how our services are delivered, how long each type of work typically takes, what we need from you before the clock starts, and how delivery is confirmed.
1. Nature of delivery
All services are delivered electronically — through deployment to a server, a handover of credentials and source code, access to a dashboard or repository, or a report delivered by email. No courier or physical shipment is involved, and no shipping charges apply.
2. Typical delivery timelines
Timelines start from the date we receive everything listed in section 3, not from the date of payment. Working days exclude Sundays and public holidays.
- Landing page or small website — 5 to 10 working days
- Business or corporate website — 10 to 20 working days
- E-commerce store or customer portal — 20 to 40 working days
- Custom software, CRM or ERP — quoted per scope, typically 4 to 12 weeks, delivered in milestones
- Telegram or WhatsApp bot — 7 to 15 working days after platform access is available
- WhatsApp Business API setup — 3 to 5 working days after your documents are submitted, subject to Meta's review
- Email infrastructure and deliverability setup — 7 to 10 working days, plus a warm-up period of 2 to 4 weeks before full sending volume
- Server provisioning, migration or hardening — 2 to 7 working days depending on size
- Automation, scraping or API integration — 5 to 15 working days
- Advertising campaigns — live within 5 working days of creative and account access being approved
- Maintenance and support retainers — continuous, from the start of the paid month
Where a third party must approve something — Meta business verification, WhatsApp template approval, Amazon SES production access, an app store review, a domain transfer — the waiting time is theirs and is not included in the estimates above. We tell you when something is sitting with a platform rather than with us.
3. What we need before the clock starts
- An approved written scope and the agreed advance payment
- Content — text, images, logos, product data — where you are supplying it
- Access credentials: domain or DNS access, hosting or server access, existing platform accounts, and any API keys the project needs
- Business documents where a platform requires them, in the name of the business being registered
- A single named person on your side who can give approvals
If any of these arrive late, the delivery date moves by the same amount. We will say so at the time rather than at the end.
4. How work is delivered and confirmed
- You get a working preview or staging link before anything goes live, for review and sign-off.
- On completion we send a handover email containing the live URLs, the credentials, the repository or source code where applicable, and any documentation.
- For infrastructure and larger builds, we run a walkthrough call so someone on your side knows how it works.
- Delivery is treated as confirmed on the date of the handover email. If you do not raise anything within 7 days, it is deemed accepted.
5. Support after delivery
- Project deliverables include 30 days of free bug fixing from the handover date.
- Retainer clients get support with a first response within one business day.
- Critical incidents on managed infrastructure — a site or mail server down — are responded to as quickly as we can, including outside business hours where the retainer covers it.
- Access to dashboards, monitoring and reports continues for as long as the plan is active.
6. Delays and communication
If we are going to miss a date, you hear it from us before the date, with the reason and a revised date. We would rather give you bad news early than a surprise on the deadline.
7. Contact
Email: [email protected]
Phone: +91 95129 29896