Mission Assistant helps you create, review, and manage Automation 2.0 workflows in Keela. Instead of needing to know every workflow rule or setting before you begin, you can describe what you want to accomplish, and Mission Assistant can help turn that goal into a visible workflow draft.
Mission Assistant is designed to guide workflow creation, not replace your review. You stay in control of what gets built, what gets edited, and when a workflow is activated.
What is Mission Assistant?
Mission Assistant is the AI layer across Velora’s suite of products. In Keela’s Automation 2.0, Mission Assistant helps bring AI-powered guidance directly into the workflow-building experience.
You can use Mission Assistant to help:
- Create a workflow from a prompt i.e. written instructions
- Explain what a workflow does
- Add or revise filters
- Add or revise split paths
- Add, remove or modify workflow steps
- Review your workflow before activation
- Identify missing setup before activation
- Review whether a workflow is ready to launch
- Understand how contacts may move through a workflow
What Mission Assistant can help with
Mission Assistant can support you throughout the entire workflow-building process.
Create a workflow from written instructions
You can describe the workflow you want in your own words. Mission Assistant will use your instructions to help create a draft workflow.
For example, you could write:
“Create a workflow that sends a thank-you email two days after someone makes their first donation.”
Mission Assistant may turn that into a workflow draft with:
- A trigger, such as donation received
- A filter, such as first-time donor
- A delay, such as wait two days
- An action, such as send an email
The workflow remains a draft until you review it, complete any required setup, and choose to activate it.
Explain a workflow
You can ask Mission Assistant to explain what a workflow does in plain language.
For example, you can ask:
“What does this workflow do?”
Mission Assistant can help summarize:
- What starts the workflow
- Who enters the workflow
- What filters or split paths apply
- What actions happen
- What settings affect the workflow
- What may still need setup before activation
This can be helpful when reviewing a workflow you created, checking a teammate’s workflow to find out what it does or how it works, or troubleshooting an existing automation.
Revise a workflow
You can ask Mission Assistant to help revise supported parts of a workflow.
For example, you might ask:
“Add a delay before the email sends.”
Or:
“Only continue if the donor has given more than $500.”
Mission Assistant can help update the workflow draft using supported steps and settings. After any change, you should review the workflow carefully before activation.
Set up filters in plain language
Filters decide which contacts should continue through a workflow. Mission Assistant can help interpret filter criteria written in plain language.
For example:
“Only include donors who are giving for the first time.”
Mission Assistant can help turn that into workflow logic that filters for first-time donors. You should always review the interpreted criteria to make sure it matches your intent.
Set up split paths in plain language
Split paths send contacts down different workflow paths based on criteria.
For example:
“Send donors who gave more than $500 down one path, and everyone else down another path.”
Mission Assistant can help add split paths and define the split criteria so the workflow can route contacts appropriately. Review each path before activating the workflow so you understand what will happen to each contact group.
Review readiness before activation
Mission Assistant supports the Review & Activate experience by helping check whether the workflow is ready to go live.
Review & Activate can identify:
- Missing trigger setup
- Incomplete action setup
- Missing filter criteria
- Missing split path criteria
- Donor-facing email actions that still need review
- Workflow settings that should be checked before launch
If there are blockers, you must resolve them before the workflow can be activated. If there are warnings, review them carefully before deciding whether to continue.
How to use Mission Assistant in Automation 2.0
1. Start with your goal
Begin by describing what you want the workflow to accomplish.
A helpful prompt includes:
- What should start the workflow
- Who should enter the workflow
- What should happen next
- Whether timing matters
- Whether different groups should follow different paths
Example:
“Create a workflow for first-time donors. When someone makes their first donation, wait two days, then send them a welcome email.”
2. Review the draft workflow
After Mission Assistant creates or updates a workflow, review the visible workflow steps.
Check:
- Is the trigger correct?
- Are the filters accurate?
- Are delays in the right place?
- Are split paths clear?
- Are the actions correct?
- Is anything marked action required?
3. Complete required setup
Mission Assistant can help create the workflow structure, but some steps may still require your input.
For example, you may need to:
- Select the Email Marketing email to send
- Choose a tag
- Confirm a filter
- Review split path criteria
- Adjust workflow settings
- Choose workflow entry rules
A workflow cannot be activated until required setup is complete.
4. Ask for changes if needed
If the workflow is close but not quite right, ask Mission Assistant to revise it.
Examples:
- “Add a three day delay before the email.”
- “Change this so it only applies to first-time donors.”
- “Add a split for donors who gave more than $500.”
- “Explain what happens if a contact does not match the filter.”
- “Make this workflow run only once per contact.”
5. Review & Activate
Before the workflow can run, Mission Assistant runs a review of your workflows to confirm it is ready before activating.
Mission Assistant can help identify missing setup, reveal blockers, or warnings so you can activate your workflows with confidence.
Best practices for using Mission Assistant
Be specific about the outcome
Start with the donor or team outcome you want, not just the workflow mechanics.
Instead of:
“Make an automation.”
Try:
“Create a workflow that welcomes first-time donors two days after their first donation.”
Include the trigger when you know it
If you know what should start the workflow, include it in your instructions.
Examples:
- “When a donation is received…”
- “When a contact is added…”
- “When a contact is updated…”
This helps Mission Assistant create a more accurate workflow draft.
Include the audience or criteria
If the workflow should only apply to certain contacts, describe who should be included.
Examples:
- “Only first-time donors”
- “Only donors who have given more than $500”
- “Only contacts with the Volunteer tag”
- “Only contacts who have not donated in the last 12 months”
Include timing
If the workflow should wait before taking action, include the delay in your prompt.
Examples:
- “Wait two days before sending the email”
- “Wait one week before following up”
- “Send the email immediately after the donation is received”
Review AI-generated logic carefully
Mission Assistant helps you draft and configure workflows, but you should always review the workflow before activation.
Pay close attention to:
- Who enters the workflow
- Whether the filter criteria match your intent
- Whether split paths are clear
- Whether actions are fully set up
- Whether donor-facing emails are correct
- Whether entry rules are appropriate
Keep your first workflow simple
If you are new to Automation 2.0, start with a straightforward workflow. You can add filters, delays, split paths, and additional actions once you are comfortable with how workflows behave.
Use plain language
You do not need to use technical workflow terms. Describe what you want to happen as clearly as possible.
For example:
“If the donor has given before, send them down a different path.”
Or:
“Only send this to people who have not received this workflow before.”
Ask Mission Assistant to explain before activating
If you are unsure what a workflow will do, ask Mission Assistant to explain it.
Example:
“Explain this workflow before I activate it.”
This can help you catch mistakes before the workflow goes live.
What Mission Assistant does not do
Mission Assistant helps guide workflow creation to review, but it does not replace your approval.
Mission Assistant does not:
- Automatically activate workflows without your confirmation
- Replace your review of donor-facing content
- Guarantee that every requested workflow is supported
- Bypass required setup
- Bypass Review & Activate blockers
- Create unsupported triggers, actions, or settings
- Automatically migrate every legacy automation into Automation 2.0
If a workflow includes donor-facing actions, such as sending an email, you should review the content and setup before activation.
Example prompts you can use
Here are a few examples of instructions you can give Mission Assistant:
- “Create a workflow that welcomes first-time donors after their first donation.”
- “Create a workflow that adds a tag when someone donates.”
- “Create a workflow that waits three days after a donation, then sends a thank-you email.”
- “Only include donors who have given more than $500.”
- “Add a split path for major donors.”
- “Explain what this workflow does.”
- “What still needs to be set up before I activate this workflow?”
- “Make this workflow only run once per contact.”
- “Review this workflow before I activate it.”
Important things to know
- Mission Assistant helps you create, explain, revise, and review workflows.
- Automation 2.0 workflows remain drafts until you activate them.
- You are responsible for reviewing workflow logic before launch.
- Donor-facing email actions require setup and review.
- Review & Activate must be completed before a workflow can go live.
- Some requested triggers, actions, templates, or recommendations may not be available depending on your account or release phase.