Service Scope & Onboarding
We agree what your service must do before we build it. Your written proposal defines the channels, workflows, deliverables, charges and acceptance checks for your business.
Catalyst: customer inquiries and qualification
Layla answers WhatsApp and/or Instagram inquiries using your approved business information and catalog, asks your qualifying questions and keeps conversations and customer records in your dashboard. Your team can take over a conversation.
Your scope names the channel or channels, the information Layla may use, the details she should collect and how your team receives the inquiry. Qualification does not by itself mean a booking, sale or payment has been completed.
Ascend: your website, customers and daily work
Your gift with Ascend is a free lead capture website to present your services and collect customer inquiries, at no additional website charge within the package. It adds Hasib’s sector workspace and Adiba’s offers and quotations to Catalyst. Hasib tracks the work and flags items that need attention. The workflows and automatic reminders enabled for your sector and account are specified during setup; they are not identical across all sectors.
Adiba prepares offers and quotations that need the owner’s approval. Prices must come from the approved catalog or an authorised approval. A draft does not become a customer commitment merely because an agent created it.
Coming soon to Ascend: Rasil for email newsletters and marketing to subscribers and consenting customers. You approve the campaigns and reusable follow-up sequences. Rasil is not yet active; its delivery and activation will be agreed in writing.
Ascend access is granted by the BznsFlow team after agreeing your setup. It is not a self-service purchase.
What is not automatically included
- Apex payment portals, cold email outreach, online stores, voice agents and custom integrations are not included unless expressly agreed and available for your engagement.
- An illustration, demo or roadmap item does not add a deliverable to your agreement.
- We do not promise sales, revenue or a particular lead volume unless a specific commitment is agreed in writing.
What we agree before starting
- Deliverables, exclusions, the selected sector and channels, and any existing tools to connect.
- Setup and recurring fees, applicable taxes, billing dates, renewal and cancellation terms.
- Included usage, how it is counted, and any additional usage or provider charges.
- Required information and access, delivery milestones, support availability and acceptance checks.
- The changes your team may approve and the actions that may run automatically.
Setup and launch
The setup schedule is agreed after reviewing scope and dependencies. Access delays, missing information or provider approvals can affect that schedule; a demo is not proof that a live integration is ready.
- Scope: agree the customer journey and the results the system must record.
- Prepare: you supply accurate business facts, catalog details and the permissions needed for the chosen channels.
- Configure: we set up the agreed questions, workflow and approval rules.
- Review: test representative conversations and workflows, correct issues and review the results together.
- Activate: confirm the agreed checks and enable the approved channels and automations.
How you confirm the service works
Acceptance checks follow your written scope. Examples include an approved answer, the required qualification details appearing on a customer record, a conversation handed to your team and an offer remaining in draft until approved.
Where an integration is included, we verify its actual result in the connected system. Your team confirms the business details and any physical work status; an AI agent cannot independently confirm that a repair, delivery or on-site job is complete.
Report any failure against the agreed scope through support. The Refund Policy explains the remedy when the service does not work as promised.
Changes after launch
Corrections to the agreed setup and requests for new functionality are assessed separately. Additional channels, integrations or workflows require an agreed scope and price before paid extra work starts. Existing customer agreements remain in force.