Aqyl Client Workspace Provisioning (Onboarding)

Aqyl Client Workspace Provisioning (Onboarding)

1. 01

   Confirm the client's data residency requirement before choosing a host.

   Aqyl is self-hosted on AWS, GCP, Azure, or any cloud provider. If the client is in fintech or healthcare, pick the region that satisfies their compliance posture first, because migrating a live deployment later means re-provisioning the database and re-issuing API keys.

2. 02

   Stand up a sandbox deployment and validate the REST API, WebSocket, and webhook paths.

   Aqyl is in public beta with 500+ companies, so exercise the integration surface before you commit vendor spend. Test one message send, one webhook delivery, and one WebSocket reconnect in the sandbox.

3. 03

   Create the client's application record and issue scoped API credentials.

   The Growth plan covers 10 applications, so track how many you consume per client. Issue separate keys per environment and store them in the client's secret manager, not a shared agency vault.

4. 04

   Wire end-user accounts into messaging channels, community feeds, and video or audio rooms.

   Map the client's existing user IDs to Aqyl accounts so the community feed and 1:1 messaging inherit the same identity. Enable video and audio rooms only if the client has agreed to the recording and storage cost.

5. 05

   Turn on AI-powered moderation and push notifications before inviting real users.

   Configure moderation thresholds in the admin panel and route flagged content to a client-owned review queue. Push notifications need the client's APNs and FCM credentials loaded before the first send.

6. 06

   Apply custom branding and point the custom domain at the deployment.

   Growth includes a custom domain, so set the CNAME and verify TLS before handoff. Replace default logos, colors, and email templates so end users never see the Aqyl name.

7. 07

   Connect webhook events to the client's CRM or user database.

   Subscribe to the events the client cares about (new message, new member, payment) and confirm delivery into their system. Log every webhook payload for the first week so you can debug silently dropped events.

8. 08

   Hand off the admin dashboard and document the escalation path.

   Walk the client's team through moderation, user roles, and analytics. Leave them a one-page runbook covering uptime responsibility, since self-hosting means the agency or client owns scaling and availability, not Aqyl.