woku_guide, which delivers the method and the playbooks, and design_voc_program, which proposes a listening program for your customer journey. A good agent calls them first and acts as a customer-experience consultant: it helps design, it does not just run commands.
The woku method
Every business is a customer journey, and each moment of truth decides whether the customer returns or leaves. woku protects revenue with the voice of the customer through a simple idea:- At each moment of truth you listen with a fast instrument (a rating plus a text or voice comment, in under 60 seconds): NPS, CSAT, CES, or a woku.
- Every signal triggers an action. A single signal becomes a support ticket (individual attention, built from the customer’s history). Recurring signals across many customers become an action plan (systematic improvement).
- Trackers are the connective tissue: they segment instruments by journey, moment, or locality, and that segmentation is what routes each ticket to the right destination and groups the signals into the right plan.
woku_guide
This is the tool to start with. On demand, it returns how to use woku:- With no arguments: the topic index, the method, and the rules for discovering ids.
- With
topic: a step-by-step playbook for that intent (the sequence of tools with their arguments, where each id comes from, the confirmations required, and the common pitfalls). - With
questionin natural language: it picks the best-matching playbook.
design_voc_program
It proposes a full listening program for your company. It takes, all optional, the business type, the available channels, your own journey moments, and how you want to segment, and returns a blueprint:- An example journey with suggested instruments. Sale, delivery, support, use, and loyalty are not required steps: the business’s real moments decide. If one moment needs to understand several things, it gets one Woku for that moment.
- The tracker design by journey, moment, or locality, with how each dimension routes tickets and groups plans.
- The action wiring (one signal to a ticket, recurring signals to a plan) and the concrete steps, naming the real
create_*tools, to build it.
Journeys and Wokus through MCP
propose_journey returns a draft object for review. To preserve the approved proposal, pass it as proposal to create_journey_from_brief, together with the three answers and confirm: true. This saves its names, instruments, order and settings without another model call. Omitting proposal generates a fresh proposal.
For a specific journey, woku_guide offers topic=customer_journeys. The agent asks for three free-text answers about the experience, the moments in order, and what the business wants to understand. propose_journey returns an editable proposal without creating anything; create_journey_from_brief requires confirm: true and saves a disabled journey without sending evaluations. If essential information is missing, it returns clarifications and creates nothing.
An image or MP4 is imported with upload_woku_media, which returns a woku fileId. set_journey_moment_media attaches that file to one Woku moment without replacing the others. create_woku creates a standalone Woku; it does not assign an existing instrument to a journey. The agent reviews the result, configures moment credentials, and only then activates the journey with update_journey. See the agent-specific options and local upload.
Recommended flow
- Call
woku_guidefor the method and the playbooks. - For a broad program, use
design_voc_program. For a concrete journey, usepropose_journeywith the three business answers. - After approval, save the journey disabled with
create_journey_from_brief, passing the revieweddraftasproposal. Complete media and connections, then activate it. For standalone instruments, use thecreate_*tools and distribute them withsend_*. - From then on, let every signal trigger its action: tickets for individual attention, plans for systematic improvement.