Your intent, the people you need to hear from and the decisions their answers should inform.
02
Plan
Design the conversation and what to measure together, around that purpose.
03
Find
Agree who takes part and how your team will invite them.
04
Talk
A participant agent conducts each individual conversation by voice or text.
05
Discover
The results bring supporting words and missing information into view.
06
Back to you
Your team explores the evidence and chooses the next question or action.
01 / Start with a purpose
Who do you need to talk to, and why?
A custom journey starts with an intent: something your team needs to learn from people. The conversation and its measurement are designed together. What you ask should help you understand the question that brought you here.
The same six steps connect the work: Brief, Plan, Find, Talk, Discover and Back to you. Your people, your purpose and the evidence you need shape what happens within them. A custom journey is built on aikho’s platform rather than treated as an isolated transcript.
02 / A platform already in use
Two journeys show the approach.
Hiring turns a role brief into candidate conversations and assessments against its requirements. Your team can review the answers behind the result and decides whom to shortlist and hire. The journey is available to start on Starter.
Customer feedback begins with a business question about an offering. Customers explain their experience; the team explores findings, participant counts and supporting words. Campaign access is switched on for a workspace by our team. These two journeys are the proof of the shared approach.
03 / Conversations worth exploring
Look for a recurring need to understand people.
Good starting points include intake conversations with experts or suppliers, onboarding check-ins, exit conversations and research panels. Some teams may want to explore eligibility or compliance interviews. These are patterns to discuss, not products being offered as ready-made journeys.
The scoping conversation establishes the purpose, who takes part, how people are invited and what the results need to support. It also identifies the limits and review that the work requires. We do not assume the same conversation design fits every setting.
04 / From idea to pilot
Design it. Test it. Put it to work.
We begin with a scoping call. Then we design the journey: your intent, the conversation, what to measure and how results should be reviewed. A useful design makes clear what an answer can establish and what still needs another check.
Next comes the build and testing with simulated participants. A pilot with real people helps examine the experience and the evidence it returns. Running and improving the journey follows that learning. Timing, price and the engagement’s boundaries are agreed during scoping.
05 / What comes together
An agent with your team. An agent with each person.
The team agent helps prepare the work and explore results. The participant agent conducts the conversation by voice or text. The results console brings back the material your team needs to review.
Your workspace has owner and member access. The journey’s scope determines its participants, available languages and operating terms. We agree those details with you rather than promising a universal configuration. Start by explaining who you need to talk to and the decision their answers should inform.
A closer look
Your questions.
How long does a custom journey take?
We agree timing in the scoping call. The purpose, conversation design, measures, pilot and operating needs all shape the work. We start by understanding the outcome your team needs, then agree the build and review steps before setting an engagement plan.
How is it priced?
We agree pricing in the scoping call. Custom journeys are scoped per project. Tell us who you need to talk to, why, and the volumes you expect, so we can discuss the work and terms. The Hiring Starter allowance does not apply to a custom engagement.
Which languages can we use?
We agree the languages for your journey during scoping. The existing journeys show what is available today: Hiring supports English and French, and Customer feedback supports English, French and Arabic. A new journey needs its own conversation design and review in the languages it will offer.
How are data and operating terms agreed?
Bring your data handling, access and procurement questions to the scoping call. The engagement needs agreed terms for its purpose and operating needs. The marketing site does not make a country-specific hosting promise or replace the agreement for the journey.
Can a custom journey become prebuilt?
That possibility belongs in the scoping discussion. We do not assume a custom engagement becomes a publicly available product. The Journeys page lists what is available, and a future prebuilt journey will be named only when it is actually being built.