Implement BotMarketing and Hand It Over to an Agency Client
By BotMarketing.pro published updated
An agency can help a small business configure an existing product when the required workflow fits that product. The practical decision is which requirements configuration will satisfy, what the client pays the agency to deliver, and who operates the process after handover.
Consider a fictional tailoring shop that needs fitting appointments. The requirements table, BotMarketing workflow, sample launch scope and support matrix below separate a SaaS referral from paid delivery. This is not a customer case or a promise of additional agency revenue.
Document the client's essential requirements first
Establish who handles appointments, how long a fitting takes, where staff confirm it and who maintains the schedule. Ask about external systems and whether visitors use Telegram. A small budget alone does not establish product fit; also check the client's language and market.
| Requirement | When to consider SaaS configuration | What needs separate assessment or delivery |
|---|---|---|
| Visitor journey | The demonstrated service and time selection suits the client | An essential step cannot be reproduced in the current interface |
| Channel and language | Visitors are comfortable with Telegram and the language has been checked | Another channel, standalone app or unconfirmed localisation is essential |
| Scheduling | The configured intervals and duration represent the appointment | Multiple resources or external calendars require an unverified connection |
| Integrations | The workflow operates without essential external synchronisation | Accounting-system exchange needs interface, data and error-handling checks |
| Access and data | Available roles and data-handling terms are acceptable | Special permissions, data portability or hosting requirements need confirmation |
| Operation | A client contact owns appointments, content and subscription payment | Nobody can operate the process or support is outside the budget |
Record evidence for each essential requirement: a checked screen, current documentation or a provider response. Do not add scores so that several conveniences outweigh one unmet essential requirement. Mark an unverified integration as a question rather than an available feature or a prohibition.
There are three possible decisions: a direct referral, a referral with scoped agency implementation, or a separate solution assessment. Where discovery and first contact are the issue, compare the roles of Telegram, Instagram and the website before moving every customer interaction into one channel.
Show the client a fitting appointment in BotMarketing
The fictional shop sees one visitor for a thirty-minute fitting. Garment production, final pricing and completion dates are separate agreements.
- The company prepares booking. In its company account, it creates an active Fitting service with a 30-minute duration, description and price, enables booking availability and configures a schedule. It connects a Telegram bot and enables reservations in the bot settings. The agency assists with the agreed configuration and checks the client screen.
- The visitor chooses a time. They open the company MiniApp from the bot, choose the service and an available slot, and leave an organisational comment. The service checks the interval and creates a booking request with a linked order; the comment is saved with both.
- Staff process the request. In Bookings, the employee opens the entry and linked order as needed, reads the comment, checks visit details and confirms the time. A submitted request does not mean the fitting has happened.
- The shop delivers the service. Staff meet the visitor and agree further work. Payment, manufacture and reconciliation with an external calendar do not follow automatically from the booking. The agency hands over the operating steps.
Before recommending the workflow, complete it using fictional data and separate visitor and staff roles. Record the date, subscription plan and result of each step rather than presenting documented capabilities as a completed test. The single-practitioner booking example covers duration and confirmation, while the product learning guide helps organise evidence.
Separate the subscription, commission and agency work
The client pays for BotMarketing access under the selected plan. The agency's separate fee covers agreed preparation, configuration, checks and training. Possible referral commission concerns customer acquisition; it does not automatically pay for the agency's future support.
A sample launch scope for the tailoring shop
A proposal can specify these deliverables without promising complete business automation:
- A short brief and requirements table with a decision for every essential point.
- One fitting service card, one schedule and a connected bot; the client approves the description, price and working intervals.
- Checks of time selection, comments and staff processing using fictional data, with the actual results recorded.
- One staff handover covering opening a booking, confirming arrangements, changing the working schedule and requesting help.
- A short operating guide listing settings, responsible contacts, unresolved requirements and support channels.
Quote this package and its acceptance conditions separately from the subscription. Include additional services, migration or integrations only after assessing the scope and confirming how they can be delivered. Ongoing scheduling and post-launch changes need a separate agreement; specify the support period and included revisions in the proposal.
Disclose the relationship before registration
We may receive referral commission from the service if you register through our link and pay for a subscription under the applicable terms. Our agency proposal separately covers configuration and handover. The platform decision is based on the listed requirements and assessment results.
This is sample wording, not proof that an assessment occurred. Apply the same criteria to options with and without commission. If the client restricts referral payments through its procurement policy, resolve the permitted approach before sending the link.
Standard terms for a new partner account are 30% during the first year from the referred user's registration and 5% afterwards; check your own and company-specific conditions separately. The friend parameter carries the referral code, the cookie lasts 30 days, and a partner-linked promo code takes priority for company registration. UTM labels do not replace the code. Accrual and actual payout differ; the partner programme guide explains the terms.
Hand over operation and agree support responsibilities
The agreed client representative should own the company account. The client controls contact details, sign-in methods and its bot; arrange agency access separately with the necessary permissions and within plan limits. Do not make the agency's referral account the business's only access or include passwords in the operating guide.
A matrix for post-launch questions
| Situation | Client | Agency | Provider enquiry |
|---|---|---|---|
| Price or schedule changes | Approves and updates the information using the guide | Assists if those changes are included in support | When standard configuration behaves incorrectly |
| A visitor requests a changed appointment | Staff agree arrangements and process the booking | Explains the agreed procedure when needed | When a standard action fails |
| The client journey fails | Supplies steps, time and a problem description | Checks its own configuration within the engagement scope | Receives a reproducible product issue without secrets |
| A new integration is required | Defines essential data and the required result | Scopes separate work after checking interfaces | Clarifies available capabilities; no development promise |
| The agency engagement ends | Checks its access and assigns an operating contact | Hands over the guide and ends agreed access | For account and standard product-operation questions |
This matrix is a basis for agreement, not a BotMarketing promise of free support or a resolution deadline. Agree channels, response expectations and included work separately. Microsoft's shared responsibility guidance explains the general distinction around data and access in SaaS; it does not replace the specific provider's terms.
For acceptance, ask the client's employee to complete the working route independently, locate the comment and explain where a problem should go. Record checked steps, open questions and their owners. Evaluate the package using actual service fees, delivery effort and support work; do not count future commission as guaranteed payment for work still to be done.