Hello Alex Docs
Tasks Overview
Create compact, reusable objectives for calls and SMS workflows. Read the Tasks guide in Hello Alex documentation.
Overview
Tasks are useful when you need repeatable outcomes with less setup than a full pathway.
How it works
- A task stores goal-oriented instructions that can be selected in launchers, reducing duplication across repeated outreach patterns.
- Published tasks become reusable building blocks, while variables allow personalization at launch time.
Use cases
- Simple reminder scripts
- Lightweight follow-up calls
Tips
- Good to know: tasks work best for narrow objectives with minimal branching complexity.
Task List
Task inventory helps teams quickly choose stable, approved objectives.
Review drafts and promote only tested tasks to published status.
- List view distinguishes draft from published assets so launchers only surface ready options.
- Clear naming and status improve selection speed and reduce accidental use of incomplete drafts.
- Published: Only published tasks appear in launchers.
- Good to know: naming tasks by outcome makes launch-time selection faster under pressure.
- Library curation
- Launch-time asset governance
Task Editor
Editor controls define what Alex should accomplish and in which channels that goal applies.
Test the task with representative inputs and publish once outcomes are stable.
- Goal text and channel settings establish expected behavior boundaries for each invocation.
- Publishing locks in a reusable version, creating consistency across repeated launches.
- Goal: What Alex should accomplish.
- Good to know: measurable goal language makes post-launch quality checks easier.
- Call objective standardization
- SMS goal templates
Variables
Variables make tasks adaptable by injecting launch-specific context at runtime.
Validate variable mappings with a small test file before broad batch use.
- Required inputs enforce completeness, ensuring key personalization data is always present when the task runs.
- CSV and launcher mappings substitute values into task prompts, making one task reusable across many contacts.
- Required variables: Must be provided at launch.
- Good to know: variable names aligned with CSV headers reduce mapping errors during high-volume sends.
- Dynamic outreach personalization
- Template reuse across segments
Next step
Publish one task for your highest-frequency outreach goal and validate it in a small launch.