Understand the visitor before recommending a path.
A parent, an adult singer, a songwriter, and a company looking for a CUDA experience should not receive the same opening script.
Adriana Granobles / Music, voice, and transformation platform
A website that can listen before it asks.
The platform had to hold a wide creative practice without making visitors decode it alone. The rebuild created a clear, editable foundation. This case then explores how a conversational assistant can understand intent, guide discovery, and hand useful context to a person.
Red Sphere rolePlatform direction / RED-CMS modernizationConversation design / guided discovery / human handoff
Canonical routes28
Migrated articles181
PlatformRED-CMS
Assistant roleGuide + qualifyWith human handoff
01
The visitor problem
One person can arrive with many different needs.
Adriana’s work spans individual music lessons, vocal technique, songwriting, the CUDA online choir, recording, events, and transformation programs. A conventional navigation system can describe those offers, but it cannot always translate a visitor’s unfinished question into the right next step.
That makes the assistant more than a floating FAQ. Its job is to reduce ambiguity without replacing Adriana’s judgment—or confusing a chat interaction with a qualified lead or payment.
“I want to sing with more confidence.”“Which program is right for my child?”“Can I join CUDA from another country?”“I need help producing an original song.”“Could this work for my company or event?”
02
The platform foundation
Modernize before automating
Give the assistant a system worth navigating.
The site was first made clearer, editable, searchable, and safer to operate. That work gives a future assistant defined routes, approved content, and real destinations instead of a pile of disconnected answers.
- 01
Organize the offer
Music classes, CUDA, songwriting, events, recording, and voice-transformation work became distinct routes with clear entry points.
- 02
Preserve the story
The redesign retained Adriana’s own voice, imagery, testimonials, video, and long-form program material instead of flattening it into generic service copy.
- 03
Make it operable
RED-CMS turned a static site into an editable system with structured routes, reusable layouts, protected configuration, and a reversible deployment path.
- 04
Connect intent to action
Contact attribution can preserve the page, service, campaign, and click context needed to follow a real lead through to a confirmed outcome.
03
The conversational opportunity
Not another generic chatbot
A conversation layer with a defined job.
A useful assistant can adapt to the page a visitor is viewing, carry relevant context through the conversation, connect approved information to clear next steps, and preserve the details a person needs to follow up. The design challenge is to help visitors move—not interrupt every page.
Answer from approved program knowledge.
The assistant can use reviewed site content, program conditions, testimonials, and frequently asked questions while making uncertainty visible.
Collect only what improves the next conversation.
Interest, age group, format, location, goals, timing, and preferred follow-up can be gathered progressively instead of front-loading a long form.
Move the right context to a person.
When the visitor is ready—or the question should not be automated—the assistant can route to contact, scheduling, WhatsApp, or a human response with context intact.
Visitor / current page: singing
I’m an adult beginner. I want to sing confidently, but I’m not sure where to start.
Adriana assistant / grounded path
I can help you compare the adult singing path with CUDA. Would you like to focus on individual technique, singing in community, or both?
Illustrative conversation design—not a live customer transcript.
01 / ContextPage + campaign + declared need
→02 / AssistantGrounded answer + guided questions
→03 / HandoffContact, schedule, WhatsApp, or person
→04 / OutcomeContacted → class scheduled → payment confirmed
04
What becomes possible
Useful automation starts where the website already has context.
The opportunity is not more messages. It is better routing, better handoff, and a clearer view of what visitors actually need.
Page-aware opening
Adapt the first prompt to singing, CUDA, events, recording, or voice-transformation content.
Guided recommendation
Turn a broad ‘I want to improve my voice’ request into the most relevant next path without pretending to diagnose the person.
Structured lead context
Pass source page, selected service, campaign parameters, and declared intent into the existing lead workflow.
Conversation analytics
Review transcripts and top intents to improve content, routing, and the assistant itself—not to inflate a vanity conversion count.
Branded interaction
Use an embedded or floating experience styled to feel native to the Adriana platform on desktop and mobile.
Voice as an option
Explore speech input or voice output where it improves accessibility and fit, with an equivalent text path and explicit consent boundaries.
The interaction shown here is a platform-agnostic design direction. Any implementation still requires approved knowledge, privacy and transcript policy, escalation rules, integration mapping, consent language, analytics events, and acceptance tests.
05
The experience in context
The assistant follows the experience
Different page. Different conversation.
A CUDA visitor may need program fit, remote participation, scheduling, testimonials, or community context. A singing-class visitor may need age, format, technique, or location guidance. Page context lets the assistant begin closer to the real need.
What the work establishes
A modern platform now. A more useful conversation next.
- 28 canonical routes and legacy paths verified through migration
- Editable RED-CMS foundation with protected configuration and rollback evidence
- Program-specific content, testimonials, video, and calls to action preserved
- Contact attribution structured around commercial lead stages—not bot activity alone
- Conversational assistant direction defined around grounding, routing, measurement, and human handoff
Website screenshots show the current public Adriana Granobles experience and its existing assistant surface. Conversation diagrams, interface copy, and capabilities on this page illustrate a platform-agnostic design approach, not a record of live customer conversations.