Allentics IT Solutions

Delivery Policy

Last Updated: December 9, 2025

This Delivery Policy governs the delivery, acceptance, completion, suspension, and revision of services and deliverables provided by Allentics IT Solutions Pvt. Ltd. ("Allentics", "we", "our", "us").

This Policy forms an integral part of:

  • Terms of Service
  • Refund Policy
  • Any Statement of Work (SOW)
  • Any Service Level Agreement (SLA)

By purchasing or using our Services, you agree to this Delivery Policy.

1. Purpose & Scope

This Policy defines:

  • When delivery timelines begin
  • What constitutes delivery
  • What constitutes acceptance
  • How delays are handled
  • How scope changes are managed
  • When delivery is considered complete

This Policy applies to:

  • Automation system setup
  • AI agent deployment
  • Workflow configuration
  • Integrations
  • Dashboards
  • Managed service onboarding
  • Enterprise implementations

2. Definitions

  • Deliverables – configured automation systems, workflows, integrations, dashboards, and related components
  • Scope Document – written onboarding document, proposal, SOW, or contract defining deliverables
  • Delivery Date – target completion date committed in writing
  • Acceptance Period – time allowed for review and acceptance
  • Business Day – Monday to Friday excluding public holidays

3. Delivery Prerequisites (Critical Section)

Delivery timelines commence only after all prerequisites are fulfilled.

Prerequisites include:

  • Full payment of setup / onboarding fees
  • Written confirmation of final scope
  • Provision of:
    • Platform credentials
    • API access
    • Business rules
    • Content and templates
    • Approval authorities
    • Compliance confirmations

3.1 Client Responsibility

The Customer is solely responsible for:

  • Timely access provision
  • Correct credentials
  • Accurate data and content
  • Internal approvals
  • Third-party registrations

Failure to meet prerequisites will:

  • Automatically pause delivery timelines
  • Shift delivery dates accordingly
  • Not constitute delivery failure
  • Not create refund eligibility

4. Delivery Timelines & Estimates

Indicative delivery timelines are:

  • Starter Plans: 1.5 – 3 weeks
  • Growth Plans: 2 – 4 weeks
  • Enterprise Plans: As per custom written scope

These timelines include:

  • System configuration
  • Integration setup
  • Testing
  • Initial calibration

4.1 Nature of Timelines

All timelines are:

  • Estimates, not guarantees
  • Dependent on external approvals
  • Subject to complexity and dependencies

Delivery dates are target dates, not contractual guarantees, unless explicitly stated in a signed SLA or SOW.

5. Delivery Dependencies & External Factors

Delivery is dependent on multiple external systems including:

  • WhatsApp Business API
  • Meta approvals
  • Google APIs
  • CRM providers
  • Cloud infrastructure
  • Third-party integrations

Allentics is not responsible for delays caused by:

  • API approval backlogs
  • Platform policy changes
  • Account verification delays
  • Third-party outages
  • Regulatory or compliance requirements
  • Rate limits or provider restrictions

Such delays:

  • Do not constitute delivery failure
  • Do not trigger refunds
  • Automatically extend timelines

6. Flexibility Buffer & Timeline Adjustments

All deliveries include a built-in flexibility buffer of up to fourteen (14) calendar days to account for:

  • Technical complexity
  • Multi-channel orchestration
  • Testing and stabilization
  • API verification delays

If additional time is required:

  • Allentics will notify the Customer
  • Provide revised estimates
  • Continue delivery in good faith

Timeline adjustments do not constitute breach, default, or delivery failure.

7. Delivery Phases (Important for Enterprise)

Delivery may occur in phases:

  • Phase 1 – Configuration
    • Workflow design
    • Channel setup
    • Rule definition
  • Phase 2 – Integration
    • API connections
    • CRM linking
    • Authentication
  • Phase 3 – Testing & Calibration
    • Functional testing
    • Sample data testing
    • AI calibration
  • Phase 4 – Deployment
    • Activation
    • Monitoring
    • Initial stabilization

Partial phase completion constitutes partial delivery and is billable and non-refundable.

8. Delivery Completion Criteria

A Deliverable is considered successfully delivered when:

  • Agreed workflows are configured
  • Core automations are active
  • Integrations are connected
  • Dashboards and logs are operational
  • Basic functional testing is completed

Delivery does not require:

  • Business performance optimization
  • Full conversion tuning
  • Revenue validation
  • End-user training
  • Zero-defect perfection

Delivery means technical readiness, not commercial success.

9. Acceptance Procedure & Deemed Acceptance

9.1 Acceptance Review Period

Upon delivery notification:

  • The Customer is granted seven (7) calendar days to review the Deliverables
  • During this period, the Customer may:
    • Test workflows
    • Report material defects
    • Request corrections strictly limited to the agreed scope

9.2 Deemed Acceptance

If:

  • No written objections are received within the Acceptance Period, or
  • The system is used in production, or
  • Live traffic is processed

Then:

👉 Delivery is deemed automatically accepted.

Accepted Deliverables are:

  • Final
  • Non-refundable
  • Eligible only for post-delivery optimization

10. Defect Classification & Correction

Only material defects affecting core agreed workflows qualify for correction.

The following are not considered defects:

  • Performance tuning
  • Conversion improvements
  • UX preferences
  • Business logic changes
  • Feature requests
  • Channel expansion

Allentics will:

  • Correct material defects within reasonable time
  • At its sole discretion
  • Without extending refund rights

11. Scope Boundaries & Change Management

Delivery includes only the items defined in the written Scope Document.

The following constitute scope changes:

  • New channels or platforms
  • Additional workflows
  • New integrations
  • Logic redesign
  • Performance optimization
  • New AI behaviors
  • Compliance modifications

Scope changes require:

  • Written approval
  • Revised timelines
  • Additional fees

Unlimited revisions are not included unless contractually agreed.

12. Post-Delivery Optimization & Support

After acceptance:

  • Minor tuning may be provided under active subscription
  • Monitoring and maintenance continue
  • Support is provided on best-effort basis

Major enhancements require:

  • New scope
  • Separate delivery plan
  • Additional fees

13. Delivery Suspension Rights

Allentics may suspend delivery if:

  • Payments are overdue
  • Required access is missing
  • Client becomes unresponsive for more than 5 business days
  • Policy violations occur
  • Security or compliance risks are detected

Suspension:

  • Pauses timelines
  • Does not trigger refunds
  • Does not waive payment obligations

14. No Performance or Outcome Guarantee

Allentics does not guarantee:

  • Conversion rates
  • Lead quality
  • Revenue growth
  • Message delivery success
  • AI accuracy
  • Business performance

We deliver technology systems, not business results.

15. Enterprise Agreements & SLAs

For enterprise Customers:

  • Delivery may be governed by:
    • Master Service Agreement
    • Statement of Work
    • Service Level Agreement

In case of conflict, the signed enterprise agreement prevails over this Policy.

16. Documentation & Audit Trail

Allentics may maintain:

  • Delivery logs
  • Deployment records
  • Change history
  • Acceptance confirmations

These records constitute official evidence of delivery and acceptance.

17. Amendments

Allentics may update this Delivery Policy at any time.

The latest version applies to future deliveries and will be published on this page.

18. Contact for Delivery & Implementation

For delivery status, timelines, or implementation support:

Email: support@allentics.com

Phone: +91 7350932100