kakinang INSIGHTS · 2026-11-04
Set up AI service: accounts, customer data and launch checks
Start AI Help me check the information, staff access, customer data and tests needed before launching AI customer service. customer service with approved public facts, a brand voice, a person responsible for exceptions and clear access to customer data. Test your own customer journeys before opening it to visitors.
Prepare information and voice
Maintain product or service pages, FAQs and contact details in the console. A public website can be added as a knowledge source and synchronized. After changes, run synchronization again, inspect its result and test representative questions; do not promise a fixed update time. Set and apply the assistant's role and tone. Tone does not grant new permissions or create business policy.
Assign staff access and handoff
Choose disabled, asynchronous or live human handoff to match staffing. For email notices, configure recipients and verify delivery. Give staff roles appropriate to their work; available actions also depend on the plan and enabled features. For multiple locations, check each account's actual visibility instead of assuming a location name isolates data.
Protect visitor identity and contact details
- Visitors may use enabled Google or LINE sign-in. In web chat, open visitor sign-in from the plus control beside the message box. After signing in, choose Link current conversation and consent to connect this thread to that identity; signing in alone does not link every older thread. Cross-channel linking requires identity evidence and customer consent. Authorized staff can help verify and associate records in the console, but a matching name or phone number is insufficient. Linking does not grant every colleague access: records remain subject to that business account’s permissions and visibility. A consented enquiry is saved in the business console for authorized follow-up; it is neither a business application nor account activation. Handle access and deletion under actual permissions, business policy and legal duties, without promising one retention period.
Check bookings, orders and launch
Configure services, schedules and cancellation terms before offering booking. A customer reviews a summary and explicitly confirms; changes or cancellation depend on identity, current status and policy. Orders need a reviewed price and contents. Payment requires separate activation and verification; a manual payment instruction is not proof of online payment. Before launch, test ordinary and unknown questions, enquiries, notices, handoff and repeated confirmation. Ask the team to assess plans, pricing and limits for your needs.
Questions teams ask
Can I change the assistant's voice?
Yes. Set and apply its role and tone in the console, subject to the plan, permissions and safety boundaries.
Are Google and LINE visitors automatically merged?
No. Linking across channels requires identity evidence and consent, not a matching name or phone number.
Who sees an enquiry?
Staff with the relevant permission in that business's console can review and follow up. An enquiry does not activate an account.
When should I go live?
After checking public facts, access, notices, relevant transactions and representative conversations against the enabled configuration.
Sources and further reading
- Knowledge management — kakinang
- Customer reception — kakinang
- Privacy policy — kakinang