In this guide
What you’ll finish with
A decision based on the client’s existing support process and the service your agency will maintain.
Before you begin
- The client’s current helpdesk and team process, if any.
- The customer task and follow-up requirements.
- A shared source set and acceptance tests.
Map the client’s existing operation
Record where conversations arrive, where staff reply and how work is assigned. Include email, website chat and social channels that are part of the current operation.
If the client already uses a helpdesk, assess the cost and effect of changing that process. If there is no staffed support operation, do not describe an agent as creating one by itself.
Operating model record
Customer channels: [record]. Current inbox or helpdesk: [record]. Team and working hours: [record]. Routine answers: [approved sources]. Requests requiring staff: [owner and destination]. Required reporting: [evidence and cadence].
Check Fin’s current integration options
Fin is offered with Intercom and with supported existing helpdesks. Its integration information includes helpdesk and data connections, so a comparison should not assume that every Fin deployment requires moving the client to Intercom.
Review the supported setup for the client’s actual system and required channels. Confirm the plan, team workflow and integration work directly in the current product information.
Build the equivalent client task in Kuga
In KugaClient workspace › Knowledge
Prepare Knowledge from the approved sources, then configure Contact Requests or Scheduling for the visitor’s next step. Use Agent > Configuration, Appearance and Test to prepare and review the public experience.
For a live staff takeover in supported channels, review Human Handover on Advanced, including its enablement, assigned people and workflow. If the team will respond later through a request, test that route instead and describe the expectation accurately.
- Prepare the same source set.
- Configure the answer and response boundaries.
- Set the required enquiry or booking path.
- Configure and test handover if included.
- Check the actual result the team receives.
Compare the complete staff journey
In each model, test a routine answer, missing information and a question that needs a person. Observe where the team finds it, what context is available and how the reply reaches the visitor.
Also check maintenance and client reporting. In Kuga, inspect the relevant conversations, request records and available Insights report. Include any external delivery work required by the client’s process.
| Question | Evidence |
|---|---|
| Where does the staff task arrive? | The actual inbox, request or helpdesk record |
| Who can act on it? | Configured access and assigned people |
| What does the visitor expect? | The tested confirmation or handover wording |
| How are sources maintained? | A completed source update and retest |
| How is the service reviewed? | Report coverage and confirmed client outcomes |
Choose the model the client can operate
Compare the required plan, staff process and agency maintenance work. Keep the client’s essential requirements at the centre of the decision. More features do not resolve an unclear follow-up owner.
Record the dependencies and unresolved checks before quoting the service. Use the proposal to explain who maintains knowledge, who responds and what is included in ongoing review.