Agree what the agency is delivering
Define whether the work includes installation, configuration, a client walkthrough or ongoing operational support. Answering customer messages is a separate service from building a website. Do not let an agency employee become the default responder simply because their Telegram account was convenient during testing. Name the client's responsible person and clarify which tasks remain with the agency after launch.
A hypothetical studio installing chat for a restaurant and a repair business should discuss their routines separately. The restaurant may ask about bookings; the repair business may need service qualification. Identical installation code does not mean identical coverage or wording. This is an example of planning across clients, not a claim about measured agency efficiency or an automatic client-isolation feature.
Keep account control and site identity clear
Decide the account arrangement with the client and verify available access controls rather than assuming a particular role model. The business needs a recoverable route to manage its service. Document who can change site settings and the Telegram connection. Avoid leaving essential access tied only to an employee or contractor who may no longer work on the project.
For each website, record its domain, responsible business contact, installation location and intended interface language. When multiple sites are managed, check that each sample conversation is associated with the correct website. Visitker provides page context, but the operator must still understand which client's request is being handled. Use non-sensitive test content and avoid including one client's real data in another client's walkthrough.
Verify every installation independently
A widget placed in a common template can appear on many pages, but one successful homepage test does not establish that all client sites work. Open a representative page on each domain, send a sample question and check the return reply from the intended operator interface. Include mobile layouts and pages where overlays, navigation or forms could compete with the chat.
Record the test result and the exact installation location so a future developer can inspect it. Check the served page after template or deployment changes, not merely the source file in a local checkout. If a client uses another party for hosting or maintenance, explain the narrow integration requirement clearly. Do not promise compatibility with every future template without inspecting the actual environment.
Handover the routine as well as the code
Show the client how a visitor writes, how the operator receives the enquiry and where the answer returns. Explain that the visitor does not need Telegram and that interface languages do not translate messages. Ask the client to perform a complete test themselves. This verifies their understanding and catches phone settings or ownership assumptions that the agency's own test cannot reveal.
Provide a short handover containing installation details, account responsibility, contact hours and a route for technical issues. At the end of the engagement, review access and remove unnecessary agency access through the supported controls. If an installation changes, preserve the business's other work and recheck the exchange. Multiple-site convenience is valuable only when each client can understand and maintain their own contact channel.
Decision table
| Decision | Record | Handover check |
|---|---|---|
| Account ownership | Business owner and access arrangement | Client can manage the service |
| Installation | Domain and exact template location | Future maintainer can find it |
| Operator connection | Responsible person and chosen workflow | Client performs a round-trip test |
| Ongoing service | Agency and client responsibilities | No unanswered ownership assumptions |
Before you connect
Can an agency manage several websites in Visitker?
Yes. Keep a record for each site's identity, operator responsibility and installation. Test every domain independently. Multiple-site management does not by itself establish the account or access arrangement that a particular client needs.
Should the agency answer client enquiries?
Only when that service is agreed. Installation support and customer support are different responsibilities. Make the boundary explicit so real visitor questions do not land with someone who lacks the information or authority to answer.
What belongs in the final handover?
Include who controls the account, where the widget is installed, who replies, which languages are covered and how to report technical issues. Have the client send and answer a sample question using their own working devices.