Client guide · Support and customer relationships
Onboard and support a remote customer service team
Customer support, Customer Success and customer care: prepare people to understand your offering, resolve requests and improve the customer experience, with an organisation suited to working across all 54 African countries.
For support, Customer Success, operations and HR leaders, and new colleagues.
Kernel / Customer Care Playbook
01
Understand
Your offering, customers and commitments.
02
Resolve
The right tools and the right decisions.
03
Support success
Adoption, quality and lasting relationships.
Updated: 16 October 2026
The Kernel perspective
A helpdesk login does not transfer business knowledge.
Quality starts before the first conversation. Your colleague needs to understand what the business sells, what it promises, what customers want to achieve and which decisions they may make. A manager, product owner, buddy and escalation contacts make that knowledge accessible. Tools support this organisation; they do not replace judgement, training or accountability.
01. Define the roles and decision authority.
Reactive support and proactive Customer Success complement one another without being interchangeable. Define channels, accounts, languages, hours, customer types, product scope and action boundaries for each role.
First-line customer support
Welcome, clarify, categorise, resolve documented requests and leave useful records. Agents should recognise urgency and ask for help without being penalised. Define permitted actions, such as simple corrections or capped refunds, together with approval and audit requirements.
- No refunds or contractual commitments outside delegated authority.
- An accountable case owner even after a handover.
Second-line technical support
Investigate further, reproduce problems and collaborate with product or engineering. Provide a sandbox, approved logs, versions and escalation criteria. Technical support does not automatically receive production administrator access.
- Distinguish incidents, product defects and enhancement requests.
- Share facts, impact, reproduction steps and redacted evidence.
Customer Success Manager
Support adoption, build a success plan and identify account risks. The CSM should not become a permanent overflow queue for support. Define ownership of renewals, expansion, discounts and commercial decisions.
- A customer business outcome and shared milestones.
- An explicit handover between sales, implementation, support and the CSM.
Customer care and back-office operations
Handle administration, orders, billing or complaints according to the business. Separate data entry, review and approval. Document identity verification, disputes, acceptable evidence and applicable statutory deadlines with qualified owners.
- Payment errors or suspected fraud follow a dedicated route.
- Managers own capacity, quality and employee protection.
CRM and customer context
Prepare a matrix for each contact reason: owner, permitted actions, any limits, approver and escalation route.
02. Prepare a workstation and a team that can sustain the workload.
Keep the foundations from the other Kernel guides: a human welcome, working arrangements, business accounts, documentation and an available team. Audio quality and confidentiality are particularly important here.
A workstation ready for real conversations
Test the computer, memory, supported browsers, display, headset microphone and acoustic environment. Make an inbound and outbound call, handle a chat and share a screen from the actual workstation with the required applications open. Specifications alone are not an acceptance test.
- Primary connectivity, backup Internet and power arrangements suited to local conditions.
- A confidential workspace; an office may be more appropriate than home.
- Inventory, updates, locking, encryption and an IT contact.
Explicit collaboration arrangements
Announce the arrival, introduce colleagues and the buddy, and share schedules, channels and handover rules. An urgent message needs a recipient and a procedure; an always-open chat channel is not enough. Account for time zones, breaks, training and contracted hours.
- Business email, individual accounts, SSO and MFA where available.
- Least privilege, a team vault, recovery and documented offboarding.
- VPN, Zero Trust or IP allowlists only when required and approved; a VPN does not guarantee a fixed IP.
Communication and video meetings
Documents and shared knowledge
Device management and protection
Identity, SSO and authentication
Business VPN and private networking
Password vaults and shared access
Kernel can discuss equipment, workstation preparation and offices according to your needs. Approve the configuration and continuity arrangements before opening the first queues.
03. Teach your business before teaching the tool.
An agent can know Zendesk perfectly and still give the wrong answer if they do not understand your service. Build learning around real customer journeys and decisions that commit your business.
Understand customers, outcomes and commitments
Explain personas, sector terminology, use cases, the business model and the impact of disruption. Demonstrate the offering from subscription and activation through usage, billing, cancellation and support. Cover contractual commitments, exclusions and services you do not sell.
Learn the product and operating policies
Provide a service catalogue, current documentation, applicable pricing, return and refund policies, known incidents and sensitive procedures. Each document needs an owner, version and review date. Separate public information from internal instructions and explain where to ask questions.
Practise without exposing a real customer
Prepare test accounts and fictional cases: blocked access, a disputed invoice, an outage, dissatisfaction and an adoption barrier. Ask the colleague to explain the diagnosis, choose a procedure, draft the reply and identify the limit of their authority. Do not copy unnecessary real customer data into training materials.
Observe, practise and gain approval
Start with demonstrations or authorised observation, then paired handling and gradually reduced supervision. Define a competency approval rubric for each reason and channel. Someone may be independent on routine email while still needing support for a disputed call or critical incident.
Support knowledge base
Training and internal certification
Deliverables: a product journey, glossary, five practice scenarios and observable competency approval, not just a completed video.
04. Build a resolution process, not just an inbox.
Email, chat, phone, forms and approved messaging channels need coherent tracking. Customers should not repeat their story whenever they switch channels.
- 01
Welcome
Listen and clarify.
- 02
Categorise
Reason, impact, priority.
- 03
Investigate
Procedures and facts.
- 04
Resolve or escalate
An action and an owner.
- 05
Confirm and learn
Outcome, follow-up and knowledge.
A transfer changes the handling team, not the obligation to follow through.
Categorise and prioritise by impact
Structure contact reason, product, account, language, channel, severity, impact and owner. An angry customer is not necessarily a critical incident; a quiet disruption may affect an essential process. Define an impact and urgency matrix, plus reasons requiring immediate escalation, including security, fraud, danger or regulatory obligations.
Make SLAs and working calendars understandable
Distinguish first response, next update and resolution time. A contractual SLA differs from the internal agreement between teams, sometimes called an OLA. Configure business calendars, time zones, start events and pause rules. An automated acknowledgement should not be counted as a meaningful response.
Transfer without abandoning the case
An escalation contains context, identity verified according to procedure, facts, impact, attempted actions, outcomes, redacted evidence and the requested next step. The recipient acknowledges ownership; the customer receives a realistic time for the next update. During a wider outage, link requests to the incident and use approved communications.
Close, reopen and learn
Explain the solution, verify the outcome or apply the agreed closure rule, document the result and provide a reopening route. Do not close cases artificially to reduce backlog. An unresolved complaint keeps its accountable owner and dedicated process even if the tool changes its status.
Omnichannel contact centre
Incidents and service communication
A useful ticket records the problem, impact, diagnosis, decision, owner and next step. It is not a repository for every piece of personal information available.
05. Prepare voice operations and difficult conversations.
Some phone tools also appear in the sales guide. Support use focuses on inbound calls, waiting, handovers, customer context and service continuity.
Validate the full telephone journey
Test caller ID, interactive voice response, skill-based routing, queues, warm transfers, callbacks, out-of-hours voicemail and ticket links. Check audio quality, latency, network restrictions, costs and use from the working country. Kernel’s coverage across all 54 African countries does not guarantee that every vendor number or feature is available.
Listen, clarify and explain what happens next
Adapt tone, detail and pace to the situation. Practise explaining a wait, a justified refusal, uncertainty and an acknowledged mistake without inventing promises. Scripts are guidance, not an obligation to recite. Train on actual service-language situations and assess written communication too.
Assist without unlimited control
For co-browsing, explain intended actions, obtain the required session permission, mask sensitive fields and let the customer stop. Never request passwords, MFA codes or payment card security codes. Visual assistance does not create blanket authority to transact on a customer’s behalf.
Protect the person taking the calls
Define how to respond to insults, threats and repeated abusive contact: supervisor support, transfer or termination according to policy, reporting and debriefing. Prepare for vulnerable customers and accessibility requirements. Include breaks, recovery and learning in the schedule.
Adapt this example: “Let me restate the issue to check my understanding. Here is what I can do now and when I will update you next.”
06. Make the right decision accessible during the conversation.
A knowledge base explains; a decision tree guides based on conditions. They work together. A decision tree never turns an incorrect policy into a compliant outcome.
The customer cannot access the service
Assess the impact and apply the required identity checks.
Known incident
Link to the incident and share the next approved update.
Documented case
Check prerequisites, follow the approved procedure and verify the outcome.
Uncertainty or sensitive signal
Pause risky actions and use the defined escalation route.
A security or fraud signal takes priority and interrupts the standard flow. Never request passwords, MFA codes or payment card security codes.
Keep knowledge reliable
Write articles from actual requests: symptoms, prerequisites, steps, expected outcome, boundaries and recourse. Restrict internal instructions to authorised colleagues. Track unsuccessful searches and unhelpful articles. Link product changes to updates in articles, response templates and guided workflows.
Build the tree with business experts
Start with a frequent contact reason and make every question, required data item, branch, exception and outcome explicit. Add an “I do not know” path and escalation. For refunds, amounts and eligibility come from an approved policy, not assumptions by an agent or an AI assistant.
Test, publish and track versions
Ask a new colleague to follow the guide with normal and edge cases. Look for blocked paths and unnecessary escalations. Assign an owner, approver and review date. An outdated procedure must be withdrawn or flagged even when it is frequently used.
Support knowledge base
Begin with a few high-volume or high-risk reasons. Publish maintainable guidance close to the agent console rather than one enormous diagram that cannot be used during a call.
07. Support customer outcomes beyond resolution.
Customer Success places support in a longer-term relationship. The objective is adoption and customer value, not merely fewer tickets.
Make the sales-to-success handover useful
Share objectives, use cases, purchased scope, stakeholders, sponsor, constraints and written commitments. The CSM checks these with the customer and agrees a success plan: expected outcome, measure, owner and next milestone. Completed training does not necessarily mean value has been achieved.
Manage adoption, risk and renewal
Track activation, meaningful usage, barriers, sponsor engagement and blocking incidents. A health score is a composite signal, not a fact about customer intent. Missing data, seasonality or reduced usage need interpretation. Define who handles alerts, leads account reviews and owns commercial discussions.
Give meetings a practical purpose
A periodic review should address outcomes, gaps and decisions, rather than become another feature presentation. When a customer is unhappy, coordinate the CSM, support and commercial owner around a clear recovery plan. Do not promise a feature delivery date that product has not approved.
Separate retention from pressure to buy
Expansion follows an established need and the agreed handover. Do not mix urgent resolution with purchase pressure. Record cancellation requests, rights and deadlines under the applicable terms; retention targets do not justify making departure artificially difficult.
CRM and customer context
A shared success plan and portfolio review may be enough initially. A dedicated platform becomes useful when the volume and data justify maintaining it.
08. Manage a service team without confusing speed and quality.
High-volume operations need forecasting, scheduling, supervision and calibration. These practices should improve service and working conditions, not introduce permanent surveillance.
A fair quality rubric and coaching process
Assess accuracy, resolution, clarity, conduct, data protection and case records. A data leak or unauthorised action is a critical error, not a small deduction offset by a good average. Sample different channels and difficulty levels, and calibrate reviewers using the same cases. Make the criteria transparent and allow results to be discussed.
Capacity planned by channel and skill
Allow time for after-contact work, breaks, coaching and training. Anticipate campaigns, launches, absence, peaks and incidents. Average handling time, or AHT, includes the defined components, such as conversation, hold time and after-contact work. Do not optimise it alone. Concurrent chat capacity depends on complexity rather than a universal target.
Operational measures defined before interpretation
Track backlog age, SLA attainment, median and upper-percentile delays, reopenings and first contact resolution. Define the observation window and same-reason rule for FCR. For telephone service level, document the time threshold and denominator, including treatment of short abandoned calls. Compare comparable situations, not raw agent rankings.
A feedback loop with product and operations
Classify recurring reasons, unnecessary effort and root causes. Assign actions to owners: correct billing, simplify a step, improve an article or fix a defect. Then evaluate effects on avoidable contacts and experience. Lower contact volume can also mean support has become harder to reach.
Quality assurance and coaching
Forecasting and workforce management
Dashboards and voice of the customer
Useful routines: a short operational review, quality calibration and a recurring customer-friction review with decisions, owners and follow-up.
09. Measure what supports decisions, then close the loop.
For greater maturity, distinguish satisfaction with an interaction, willingness to recommend and effort in a journey. CSAT, NPS and CES answer different questions and cannot be converted into one another.
The interaction
CSAT
40 / 50 = 80%
Example: 40 ratings of 4 or 5 out of 50 valid responses on a five-point scale.
Satisfied / valid responses × 100
Willingness to recommend
NPS
60% − 20% = +40
Example: 100 responses, including 60 promoters, 20 passives and 20 detractors. The result is not a percentage.
% promoters − % detractors
Journey effort
CES
A consistent convention
Example: mean agreement from 1 to 7 with “The journey was easy”, from 1 (strongly disagree) to 7 (strongly agree). Higher means less effort here; keep that convention when comparing.
Question + scale + direction
Choose the question, scale and timing
CSAT can follow an interaction; relationship NPS should be measured at a coherent point in the customer lifecycle; CES relates to effort in a specific journey. Fix wording, language, trigger, eligible population and maximum frequency. Avoid repeated invitations for the same episode. Built-in helpdesk surveys may be sufficient initially.
Use the correct denominators
For five-point CSAT where 4 and 5 are positive, divide those responses by all valid responses and multiply by 100. For NPS on 0 to 10, promoters score 9 or 10, passives 7 or 8, and detractors 0 to 6. Subtract the percentage of detractors from promoters; passives remain in the denominator. The result is a score from -100 to +100, not a satisfaction percentage.
Read the bias before interpreting the score
Report the period, response count, delivered invitations and a defined response rate. Segment cautiously by reason, channel, language, product or customer tenure. Small samples and voluntary responses may be heavily biased. Do not compare different scales, populations or timing, or turn NPS into an individual agent grade. Never select only happy customers for surveys.
Listen to comments and act
Assign follow-up ownership for feedback requiring contact, with a timeline appropriate to the risk. Customers should understand what changes or why their request cannot be met. Group recurring friction, share root causes with the right teams and assess the effect of corrections. Protect free-text feedback, which may contain sensitive data.
Dashboards and voice of the customer
A score is useful when it leads to a decision and a tracked improvement. The numerical examples above are for learning, not targets imposed on your business.
10. Protect customers and colleagues, including when using AI.
Support handles personal, financial and contractual information. Access from another country and cloud tooling should be reviewed with legal, security and data protection owners.
Minimise data and secure operations
Follow identity verification procedures before sensitive actions. Separate client accounts when serving multiple businesses and restrict exports, downloads and local copies. Use approved secure payment journeys; never put card numbers or security codes into ticket notes. Prepare for security incidents, data subject requests and access revocation.
Govern monitoring, recording and transcription
Have qualified owners approve purpose, legal basis, proportionality, information, permissions, retention and local requirements. Training or quality monitoring does not justify systematic surveillance by default. Review transcription, AI analysis and reuse of recordings separately; a recording switch is not legal approval.
Use AI as controlled assistance
Summaries, translation, knowledge search and draft replies can help after approval of terms, data and settings. Restrict sources to current approved knowledge, enforce access permissions and test errors. Colleagues review commitments, amounts and diagnosis. A customer message or attachment must not be able to issue instructions to the assistant.
Preserve a human route
Automated replies must not invent rules or conceal an inability to resolve. Plan human handover, sensitive-case escalation and false-positive review. Restrict AI agent permissions and actions, especially for refunds, contracts and accounts. Measure reopenings, errors and satisfaction, not just deflected conversations.
Identity, SSO and authentication
Password vaults and shared access
Listed tools are an editorial selection. They do not guarantee compliance, availability of every feature in every country, or Kernel partnership terms.
11. Build independence from evidence of competence.
Adjust timing to product complexity and experience. Stages are not ticket quotas; missing access or incomplete procedures are not performance failures.
Before arrival: prepare and assign
The manager and product owner approve the role, learning path, tools and practice scenarios. IT tests the workstation and accounts. Quality shares the rubric; experts approve sensitive policies, escalations and training data. Announce the arrival and reserve the buddy’s time.
Week 1: understand and simulate
Introduce the business, demonstrate the product, explore customer journeys and observe with appropriate safeguards. Use fictional cases, test calls and practise finding a procedure. Approve clarification, ticket notes, next steps and recognition of sensitive cases before opening a real queue.
Days 1 to 30: handle cases with support
Gradually open approved reasons and channels. Keep help available, review work and discuss progress. Record questions and documentation gaps. For a CSM, prepare the first account handover and review a success plan before presenting it to the customer.
Days 31 to 60: expand without losing quality
Approve more complex cases and involve the colleague in calibration. Interpret escalations, reopenings and feedback in context. For a CSM, run an assisted adoption review and document risks and agreed decisions.
Days 61 to 90: confirm and improve
Review permissions, objectives and workload. Ask the colleague to improve an article, journey or root cause. For the CSM, review progress against the success plan. Agree the next learning goals and handover rules for absence or departure.
The end of onboarding confirms which decisions the person can make, which cases they escalate and which support remains available.
The support and Customer Success tool reference
60 tools across 20 categories, with three options for each need. Suites sometimes overlap and some components are complementary: this is not a shopping list. Keep your existing environment when suitable and start with the helpdesk, knowledge and appropriate calling. Add WFM, quality, Customer Success or advanced measurement when volume and maturity justify it. Test your real cases, languages and workstation.
Independent editorial selection, with no implied partnership, discount or compliance guarantee. Features, usage costs, integrations, data locations and terms change: confirm them with each vendor. Links open official websites; their icons come from a third-party service.
01Communication and video meetings
Choose an official channel, overlap hours and an audio fallback. These suites are alternatives.
Slack
Project channels, asynchronous discussions and technical notifications.
Official websiteMicrosoft Teams
Messaging, meetings and collaboration within Microsoft 365.
Official websiteZoom Workplace
Meetings, screen sharing and collaboration subject to internal policy.
Official website
02Documents and shared knowledge
One entry point for onboarding, team documents and internal decisions. Identify the customer handling knowledge base separately.
Notion
Team wiki, onboarding paths and documented decisions.
Official websiteConfluence
Technical documentation and procedures linked to Atlassian projects.
Official websiteGoogle Workspace
Documents, calendars and files with centrally managed sharing.
Official website
03Device management and protection
Check supported operating systems, encryption, updates, inventory and lost-device procedures. MDM and EDR are complementary.
Microsoft Intune
Device management and compliance policies.
Official websiteJamf
Apple device management and security depending on the products selected.
Official websiteFleet
Device inventory and fleet management with platform-dependent features.
Official website
04Identity, SSO and authentication
Prefer SSO, phishing-resistant MFA where possible and managed offboarding. SCIM and advanced controls depend on the plan.
Microsoft Entra ID
Identity management and conditional access subject to licensing.
Official websiteOkta
SSO, account lifecycle and authentication policies.
Official websiteJumpCloud
Cloud directory and identity and device management.
Official website
05Business VPN and private networking
Compare operations, routing, DNS, throughput, recovery and Internet egress. A private tunnel IP is not a public egress IP.
Tailscale
Private networking; Internet egress requires an approved, configured exit node.
Official websiteOpenVPN Access Server
Managed VPN on infrastructure where you control routing and egress.
Official websiteWireGuard
VPN protocol and software; identity, monitoring and fleet operations still need to be organised.
Official website
06Password vaults and shared access
Use individual accounts and team vaults. A vault does not replace helpdesk permissions; avoid shared logins.
1Password Business
Team vaults, access assignment and controlled credential sharing.
Official websiteBitwarden
Business password management with collections and plan-dependent policies.
Official websiteKeeper
Credential vaults and access controls depending on subscribed modules.
Official website
07VoIP calling
Test inbound and outbound calling from the actual workstation, ticket integration, transfers and fallback. Confirm numbers, destinations, portability and use from the working country with the vendor.
Aircall
Cloud calling and CRM or helpdesk integrations; routing and supervision depend on the plan.
Official websiteRingover
Business calling, queues and integrations subject to plan and configuration.
Official websiteCloudTalk
Calling, routing and conversation tracking; check relevant coverage and costs.
Official website
08Omnichannel contact centre
Consider when queues, skills, channels and supervision become complex. A CCaaS suite can replace several components; avoid adding a second phone system without a reason.
Genesys Cloud CX
Contact centre platform, routing and journeys depending on modules.
Official websiteNICE CXone
Contact centre suite with handling and management capabilities depending on the offering.
Official websiteTalkdesk
Cloud contact centre and business integrations to validate against your scenarios.
Official website
09Helpdesk and customer conversations
Compare channels, ticket rules, SLAs, exports, permissions, hosting and integrations. AI assistants may be separate, usage-priced options.
Zendesk
Tickets, help centre and support workflows depending on products and plan.
Official websiteIntercom
Messaging and support operations; AI capabilities and channels depend on the contract.
Official websiteFreshdesk
Request management and automation; verify the selected omnichannel scope.
Official website
10CRM and customer context
Link people, company, contract, commitments and cases without duplicating identities. These suites may overlap with helpdesk tools: define the system of record.
HubSpot Service Hub
Customer service linked to HubSpot CRM, with tier-dependent capabilities.
Official websiteSalesforce Service Cloud
Case management and customer context within the Salesforce ecosystem.
Official websiteZoho CRM
Relationship history and sales data; Zoho Desk is a separate helpdesk product.
Official website
11Customer Success and adoption
Useful for ongoing account ownership. Define usage data, success plans and renewal ownership before automating health scores.
Gainsight
Customer Success management, plans and health signals depending on modules.
Official websitePlanhat
Account views, journeys and adoption management based on connected data.
Official websiteChurnZero
Engagement and retention risk tracking configured for your business model.
Official website
12Support knowledge base
Separate public articles from internal instructions. Test search, languages, permissions, approval, versions and review dates; the built-in help centre may be sufficient.
Document360
Knowledge bases and structured documentation depending on the offering.
Official websiteGuru
Internal knowledge discovery and delivery with configured governance.
Official websiteHelpjuice
Article creation and search for a dedicated knowledge base.
Official website
13Decision trees and guided procedures
Test exception paths, publishing, history, languages and console integration. A drawn diagram is not necessarily an executable or auditable workflow.
Stonly
Interactive guidance and knowledge for diagnosis and self-service.
Official websiteZingtree
Decision trees and guided workflows for service teams.
Official websiteYonyx
Decision guides and conditional scripts, with integrations to verify.
Official website
14CSAT, NPS and customer effort
Compare triggers, deduplication, survey frequency, comments, exports and follow-up loops. Start with built-in surveys when sufficient.
Nicereply
CSAT, CES and NPS surveys linked to interactions through supported integrations.
Official websiteSurvicate
Surveys and customer feedback across touchpoints.
Official websiteQualtrics
Customer experience measurement and analysis programmes depending on products.
Official website
15Quality assurance and coaching
Define rubrics, sampling, critical errors, calibration and review rights. Automated analysis does not replace human judgement or applicable employment rules.
MaestroQA
Interaction evaluation and service quality coaching.
Official websiteEvaluAgent
Quality management and support team development.
Official websitePlayvox
Quality evaluation and coaching; verify the current product and integrations.
Official website
16Forecasting and workforce management
Plan by channel, skill and interval, including breaks, training and unavailability. Validate local working rules and avoid intrusive surveillance.
Assembled
Forecasting, scheduling and operational analysis for support teams.
Official websitePeopleware
Workforce management, forecasting and scheduling adjustments for contact centres.
Official websiteCalabrio WFM
Contact centre workforce forecasting and scheduling.
Official website
17Co-browsing and visual assistance
Arrange session permission, masking, action boundaries and on-demand termination. Test sensitive data and the actual applications used.
Surfly
Co-browsing and web collaboration with controls to configure.
Official websiteGlance
Guided assistance and co-browsing for customer journeys.
Official websiteUpscope
Co-browsing to guide a customer through a web interface.
Official website
18Incidents and service communication
Support relays approved information, not improvised estimates. Test public or private visibility, subscriptions, approval and incident ticket links.
Atlassian Statuspage
Status pages and service incident communications.
Official websiteBetter Stack
Monitoring, incident management and status pages depending on products.
Official websiteincident.io
Incident coordination and status communication depending on the offering.
Official website
19Training and internal certification
Organise product learning, exercises and competency approval. An LMS does not replace coaching or an up-to-date knowledge base.
360Learning
Learning programmes and collaborative training.
Official websiteTalentLMS
Course creation, assessments and learning progress tracking.
Official websiteDocebo
Learning platform with deployment and integration requirements to define.
Official website
20Dashboards and voice of the customer
Define metrics before dashboards. Link volume, quality, time, segments and actions; minimise personal data and exports.
Microsoft Power BI
Modelling and dashboards using approved data sources.
Official websiteLooker Studio
Reports using connectors and sources with verified permissions.
Official websiteMetabase
Database analytics and dashboards with governed access.
Official website
Your support team readiness checklist
Work through this with the manager, HR, IT, product owner and colleague. Progress stays on this page and does not replace competency approval or a compliance assessment.
0 / 20 items checked
Frequently asked questions
Can one person be both a CSM and a support agent?
Yes in a small organisation if responsibilities and time are allocated clearly. Reactive resolution, proactive adoption and commercial decisions must remain distinct. When urgency consumes all available time, the success plan receives no attention.
Do we need a full contact centre from day one?
No. A helpdesk, knowledge base and integrated calling may be enough. Omnichannel suites, WFM and advanced quality tools become relevant when queues, channels, skills and volume justify them. Evaluate built-in features before adding licences.
Should we choose CSAT, NPS or CES?
CSAT measures a defined satisfaction question, often after an interaction; NPS measures willingness to recommend; CES concerns effort in a journey. Begin with the decision you need to support, not the popularity of a score. These measures cannot be converted into each other.
Can a decision tree replace training?
No. It makes an approved procedure accessible and guides expected cases. Colleagues still need to understand the offering, their authority and exceptions. Include an uncertainty route and an accountable expert to maintain the tree.
Must we record every call to evaluate quality?
No. Monitoring or recording must be necessary, proportionate and approved under applicable rules. Define information, access, retention and employment arrangements with qualified owners. Quality assessment can also use written cases and simulations.
What is Kernel’s role?
Kernel is your HR partner in Africa across all 54 countries, combining technology and local teams. Discuss recruitment, EOR, COR, HR management, equipment and offices. Your business remains responsible for service definitions, decision authority, tool selection and legal and security approvals.
Further reading
Methodological references and vendor sources for further reading. CNIL resources explain the French and European framework; they do not replace review of local rules and international processing. Content and offerings may change.
Prepare your support team across all 54 African countries
Share your mission, channels and organisational needs with Kernel. Prepare HR arrangements, equipment and colleague integration while your business owners define the customer experience to deliver.
Talk to KernelOperational guidance, not a compliance or performance guarantee. Qualified owners approve business, legal, employment and security decisions. Trademarks belong to their respective owners.