Actions

Let your Delphi jump in at the perfect moment—sending tailored messages, tagging users, and syncing data while you focus on high-value work.

What it is

Actions are self-running workflows that your Delphi carries out whenever a user hits a threshold you set—such as staying inactive for a week, buying a membership, or reaching their message limit. ​

When that trigger fires, your Delphi checks the latest context and replies just as you would: sending a personalized note, tagging the user, updating the properties associated with the user, or syncing data to another tool.

You decide the rule; your Delphi handles the rest.

Below are examples of how to use Actions:

• User-requested reminders – When someone says “remind me tomorrow,” your Delphi pings them at the exact time they asked with a message personalized to what they asked to be reminded about.

• Post-conversation plans – The moment a chat wraps up, your Delphi shares next steps over email and lists out the action items the person agreed to in their conversation.

• Inactivity nudges – After a week of silence, your Delphi checks in with a friendly “Need any help?” to keep users engaged.

• Thank-you & feedback loops – Right after signup or purchase, your Delphi delivers a warm thank-you, then asks for feedback on the product the next day to help you keep improving upon it.

• Smart tagging & data forwarding – Each time a user mentions a new goal, your Delphi adds the right tag and forwards details to your CRM.

• Weekly progress checks & conversation recaps – Every seven days—or every 50 messages—your Delphi sends a concise progress update or chat summary so everyone stays on track.

Create actions for your Delphi here →

Go to Actions if you're wondering...

• How do I make sure users stay engaged with my Delphi?

• How can I get my Delphi to proactively reach out to users on my behalf?

• How can I get my Delphi to reach out to people who have stopped using it, reminding them to come back?

• What kinds of things can my Delphi do on my behalf?

• How do I get people to come back to my Delphi after their first conversation?

---

Quick Start Guide

Click here to watch our video tutorial series instead!

1

Create a New Flow

Start from scratch, use a template, or type natural-language instructions into the prompt bar—your Delphi will understand.

2

Set Your Trigger

Choose what activates an action—whether it’s a message, an event, or a milestone. Your Delphi doesn’t just react—it responds with context.

Trigger	Condition	Use Case
Alert Triggered	User mentions a topic	Auto-respond, escalate, tailored follow-ups
Conversation Ended	5+ messages & user ends	Personalized follow-ups, trend tracking
Usage	User hits chat/call/video limit	Engagement prompts, proactive outreach
Quota Reached	User reaches usage quota	Upsells, alternative access suggestions
Inactivity	User inactive for set time	Smart re-engagement, contextual check-ins
Phone Captured	User enters phone number	Verify contacts, personalized SMS outreach
Product Recommended	Delphi recommends a product	Smart follow-ups, discounts
Membership	User subscribes	Personalized welcome, onboarding
Payment Made	User completes a payment	Premium access, tailored next steps
Specific Date/Time	Scheduled date/time reached	Contextual reminders, event-based engagement
Recurring Schedule	Set interval reached	Automated updates, sustained conversations

3

Pick Your Actions

Decide how your Delphi responds—not with generic automations, but with actions that mirror how you would naturally engage. You can add up to 3 actions per trigger.

Action	Functionality	Use Case
Send message	Sends you or your user a notification	Stay informed yourself, engage your users
Update Tag	Assigns/removes a tag from a user	Track behaviors, segment users
Update Property	Assigns/removes a property from a user	Categorize users, accumulate metadata
Custom API	Sends a POST request with user details to an API	Sync data with external systems, update CRMs, integrate analytics

4

Save & Publish

Click Save to store your flow, then Publish to activate it.

5

Monitor Your Flow

Your action is live! Adjust it anytime to refine interactions. Disable it instantly from Your Actions—green means active, red means paused. Check for activations in the activity log at the bottom of the triggers sidebar or actions sidebar: this shows you every time the trigger or action has been set off.

Click here to go to Actions in Studio and start creating personalized, context-aware workflows.

---

Full Feature Guides

Video Tutorial Series

A quick-fire playlist of step-by-step videos that walk you through everything from your first Action to advanced tooling.

Learn more

Creating an Action

Learn three streamlined methods—template, wizard, and from scratch—to spin up a new Action in minutes.

Learn more

Testing Actions

Follow a concise checklist to simulate, debug, and validate every Action before it ever touches a live user.

Learn more

Editing Live Actions

See how to pause, edit, or retire any live Action without breaking existing workflows or data.

Learn more

Triggers Guide

Browse a definitive catalog of every event that can fire an Action, with practical examples and limits.

Learn more

Actions Guide

Explore the full menu of tasks Delphi can perform for you, from sending emails to updating external systems.

Learn more

---

❗Best Practices

• Save often. Actions don’t auto-save—click Save after every major change.

• Messaging Actions Need Instructions, Not Scripts: Your Delphi is not a chatbot that follows a rigid script—it’s an adaptive digital mind. Instead of scripting full conversations, focus on guiding Delphi’s intent and tone.

To use messaging actions effectively...

• ✅ Do: Be specific and include details, being as specific and clear as possible in your instructions. Your Delphi can only use the context you provide.

• ✅ Do: Keep instructions focused, avoiding the urge to pack multiple actions into one instruction since this often generates long, unhelpful messages. A single, well-defined request with clear parameters will lead to better responses.

• 🚫 Do Not: Write scripts, since it will not follow the script. Instead, your Delphi will be confused as it is looking for a clear instruction and not a predefined message.

• 💡 Example:

  • ✅ Good: “Send a follow-up message three days after purchase asking if they have any questions about getting started.”

  • 🚫 Bad: “Hey [First Name], I wanted to check in! How’s it going? Let me know if you have questions.” or * “Send a message saying, ‘Hey [First Name], I wanted to check in! How’s it going? Let me know if you have questions.’ Then, if they don’t respond, send another message that says, ‘Just following up on my last message…’

• Custom Delays Need Clear Instructions: Custom delays help you fine-tune when and how your Delphi engages with users.

To use custom delays effectively...

• ✅ Do: Be specific and include details, being as specific and clear as possible in your instructions. Your Delphi can only use the context you provide.

• 💡 Example:

  • ✅ Good: “Send the message 2 hours after the end of the user’s event if they mention it, otherwise send it the day after their event at 8AM in the morning.”

  • 🚫 Bad: *“Send the message when it makes sense for the user based on the stuff they said.”

• Test Your Flows Before Deployment: Ensure your Delphi’s triggers and actions work as intended to prevent errors and improve user experience. See here for more information on how to effectively test your actions.

❓FAQs / Troubleshooting

Why are users not receiving my SMS notifications?

Mobile Communications Require Opt-In: Users will only receive SMS texts or phone calls if they have opted into mobile communications from your Delphi.

• To opt in: Users must enter their phone number on your Delphi’s profile page and receive a text message.

• To opt out: Users can text “STOP” at any time.

What is the difference between tags and properties?

Both tags and properties help you organize users, but they serve different purposes in how they categorize and store information.

🔹 Tags: Predefined, Broad Categories Tags are fixed categories that you create to organize users based on a shared characteristic. Every user either belongs to the group (has the tag) or doesn’t. Think of tags like giant folders where you decide in advance what groups exist, and users are added or removed from them.

• Example: You might create a tag for “Ice Cream Lovers.” If a user mentions ice cream, they get tagged.

• How it works: Tags are predefined—you decide what groups exist and manually or automatically apply them to users.

• Use case: Great for broad, easy-to-manage categories like “Beta Tester,” “VIP Customer,” or “Attended Webinar.”

🔹 Properties: Dynamic Labels Properties are custom values assigned to each user individually. Instead of sorting users into predefined groups like tags, properties store specific details that can vary from person to person. Think of properties like fields in a database—they hold different values for different users.

• Example: Instead of a general “Ice Cream Lover” tag, you could create a property called “Favorite Ice Cream Flavor” and let each user have a different value, like “Pecan”, “Vanilla”, or “Chocolate Chip.”

• How it works: Properties are flexible—you don’t need to define every possible value ahead of time. Instead, they store unique details per user.

• Use case: Best for tracking dynamic, personalized details like “Age,” “Last Purchase Date,” or “Location.”

🛠️ When to Use Each?

• Use tags when you want to define broad user groups and manually or automatically place users in them.

• Use properties when you need to store unique details for each user without knowing all the possible values ahead of time.

In summary, think of tags as quick labels and properties as customizable user data. Hope that helps! 😊