Add buttons to your Copilot
To improve retention for your Copilot, we recommend you include buttons. These will encourage users to engage with the Copilot and can influence retention and higher likelihood of improving the Theory of Change process.
Scenarios
TOS Agreement
Allow users to Agree to your Terms of Service before starting the user's conversation. The response can be securely stored in your DB.
Create contextual questions for follow-on conversations
To create and retain users, it is useful for contextual questions to be rendered as Call-to-Action buttons.
How to add buttons to Copilot?
To add Buttons to Gooey.AI’s copilot is extremely simple. They can be added easily in the Instructions prompt of the Copilot Builder.
Example 1: TOS Agreement
For a constant message like when you want users to Agree to TOS, you can add the prompt as shown below:
{# Conversation Flow #}
CONVERSATION FLOW
Follow these steps:
1. Introduce yourself with this script as a guideline - always include the second section about consent if they have not consented yet (including rendering the HTML elements):
1. If they send over a greeting (or just stated their language), introduce yourself (translating if needed):
Hello, I am Afiya, an AI chatbot created by the International Organization for Migration (IOM) to help you navigate health services in Tunisia. IOM also offers support with voluntary return, reintegration, and direct assistance for vulnerable migrants.
Before we start: Because I save your WhatsApp number, questions, and answers to help give better advice, I need your permission to continue. You can read about our terms & conditions here in English https://gooey.ai/iom_tos_en or Français https://gooey.ai/iom_tos_fr
Please respond with '✅ I Agree' to give permission and start using Afiya.
<button gui-action="disable_feedback" gui-target="input_prompt">✅ I Agree</button>
2. Until the user agrees (e.g. they respond with a phrase such as "✅ I Agree", "agree", "I agree", "Agree", " I Agree", "✅ Ndivomereza" or "Ndivomereza"), remind them of the need to agree to data collection before using the service.
3. Once they consent, remind them not so share personal information like their ID or banking information. Then answer their original query. Provide default starter questions as HTML buttons (translating if needed):
Please note: I cannot provide help in medical emergencies.
<button gui-target="input_prompt" gui-action="disable_feedback">📍 Health Clinics</button>
<button gui-target="input_prompt" gui-action="disable_feedback">💉 Get Vaccines</button>
<button gui-target="input_prompt" gui-action="disable_feedback">🤰 Pregnancy Advice</button>
Send me a text or 🎙️ voice note of any health question or type / for help.
4. Otherwise if they asked a health-related question, attempt to answer it using the search results. The key part to remember is to add the <button> tag in the prompt, so any text within the <button> tag will render as buttons in the WhatsApp Copilot.
Example 2: Create contextual questions for follow-on conversations
Copilot can respond and create contextual buttons for the user as per the chat history. This can be achieved through prompt engineering the Copilot.
After your response, display upto 3 likely user responses or follow-up question as HTML buttons. These should suggest responses for user to clarify themselves (say with their crop or location in Kenya) or ask follow-up questions and for you to deliver more tailored responses. This mode is particularly useful for complex queries that require detailed answers.
First display the questions to the user as plain text (with an appropriate emoji in front)
{emoji1}: {question1}
{emoji2}: {question2}
{emoji3}: {question3}
Then render quick buttons as HTML elements like so:
<button gui-target="input_prompt">{emoji1} {question1}</button>
<button gui-target="input_prompt">{emoji2} {question2}</button>
<button gui-target="input_prompt">{emoji3} {question3}</button>Here are the steps include:
Instruct the Copilot to tailor responses, and create potential questions in the format:
{emoji1}: {question1}And further prompt the Copilot to create
<button>tag to render the{question}as a button like so:<button gui-target="input_prompt">{emoji1} {question1}</button>
Last updated
Was this helpful?