1. Browse the pre-built templates section and select one based on either their brief descriptions or the detailed template guides below. Each template can be customized to your needs.

2. Customize your selected template’s settings. Take a look at the Triggers and Actions Guides below for a detailed explanation of how to customize each trigger and action.

3. Click “Save” in the top right corner. Now you’ve published your first Action!

1. Click the “New Flow” box in the “Start from Scratch” section.

2. Click “Add Trigger.”

3. Click the “When: User ends a conversation” box under “Trigger” to customize your trigger.

4. In the right-side popup, select your desired trigger type from the dropdown list. Below, you’ll find all available triggers with details on how they work, customization options, and best use cases.

5. Complete your trigger setup with two final choices:

6. Click “Add Action.”

7. Click the “Do: Notify the user with a Prompt via Medium” box under “Action” to customize your action.

8. In the right-side popup, select your desired action type from the dropdown list. Below are all available actions, with descriptions of how each one works and its specific configuration settings.

9. Complete your action setup by selecting when to execute the action after the trigger:

10. To add multiple actions for the same trigger, click the “Add Action” button in the top left corner. This allows you to create a second and third action, each of which can be customized independently while still being triggered by the same event.

11. Review any validation warnings or errors that appear in the top-left corner. Address these before proceeding.

12. Click “Save” to publish your flow. The status indicator will change from “Unsaved” (yellow) to “Published” (blue) when complete.

1. Use the Composer to quickly describe the Actions flow you want—no need to build it step by step. Simply type what you want your Delphi to do, and it will automatically generate the flow for you, including up to 3 actions if your request is clear. The Composer works best for triggers specific to the Actions feature, such as conversation ended, user inactivity, quota reached, usage milestone, phone number captured, payment made, a specific date/time, or a recurring schedule. But below is a full list of triggers and actions you can request:

2. Once the flow is generated, you can edit it in two ways:

​

✅ Understand It: This trigger activates when a user mentions a specific topic or concept in conversation.

⚙️ Customize It: Choose which alert to connect this trigger to, determining what type of conversation topic will activate it. Select your desired alert from the dropdown list of all your alerts. To learn more about customizing alerts, see this documentation guide.

💡 Example: If you set an alert for the keyword “pricing”, the trigger will activate when a user asks something like “How much does this cost?” or “What are the pricing plans?”. You can then decide what action this trigger causes, such as sending an automated response, escalating the conversation, or prompting a follow-up.

🎯 Use It: Automatically respond to key topics, escalate important discussions, or prompt follow-ups based on user interests.

✅ Understand It: This trigger activates when a conversation reaches at least five messages (total between the user and the Delphi) and then ends.

⚙️ Customize It: N/A

💡 Example: If a user has a five-message or longer discussion with your Delphi about career advice and then leaves, this trigger will activate. You can then decide what action this trigger causes, such as sending a follow-up, requesting feedback, or tracking conversation trends.

🎯 Use It: Send follow-ups, request feedback, track conversation trends, or initiate next steps after user interactions.

✅ Understand It: This trigger activates when a user reaches a set number of messages or minutes. It can either trigger only the first time they reach this threshold or every time they reach this threshold.

⚙️ Customize It: Choose what to track—chat messages, voice minutes, or video minutes—by selecting an option from the “What are we tracking?” dropdown. Then, set the activation threshold by entering the desired numerical limit for messages or minutes under “After how many units of usage?”

💡 Example: If you configure the trigger to activate after every 10 messages, it will fire every time a user sends a message that’s a multiple of 10 (10 messages, 20 messages, etc.). You can then decide what action this trigger causes, such as prompting deeper engagement, unlocking rewards, or guiding users through structured interactions.

🎯 Use It: Encourage deeper engagement, offer mid-conversation prompts, unlock rewards, or guide users through structured interactions.

❗ Note: Republishing or editing a Flow triggered by usage resets the user’s usage count to zero. For example, if a user had sent 7 messages toward a 10-message trigger, and you change the limit to 9, their progress resets. Instead of needing 2 more messages, they would need to send 9 again for the trigger to activate.

✅ Understand It: This trigger activates when a user reaches their usage quota while interacting with your Delphi.

⚙️ Customize It: Select the quota type to track—message limits, voice minutes, or video minutes—from the “What are we tracking?” dropdown.

💡 Example: If a user has a quota of 50 messages and sends their 50th message, this trigger will activate. You can then decide what action this trigger causes, such as prompting a subscription upgrade, offering alternative access options, or upselling users to your other products.

🎯 Use It: Prompt subscription upgrades, offer alternative access options, and upsell users to your other products.

❗ Note: Republishing or editing a Flow triggered by usage resets the user’s usage count to zero. For example, if a user had sent 7 messages toward a 10-message trigger, and you change the limit to 9, their progress resets. Instead of needing 2 more messages, they would need to send 9 again for the trigger to activate.

✅ Understand It: This trigger activates when a user has been inactive for a specified number of days.

⚙️ Customize It: Set when the trigger activates by entering a number under “Inactive for” and selecting days, weeks, or months from the dropdown.

💡 Example: If you set the trigger for 7 days, it will activate once a user has been inactive for a full week. You can then decide what action this trigger causes, such as sending a check-in message, offering an incentive to return, or reminding them about new features or updates.

🎯 Use It: Re-engage users with a check-in message, offer incentives to return, or remind them about ongoing features or updates.

✅ Understand It: This trigger activates when a user enters their phone number.

⚙️ Customize It: N/A

💡 Example: If a user provides their phone number during a conversation, this trigger will activate. You can then decide what action this trigger causes, such as verifying their contact details, enabling SMS-based interactions, or triggering follow-ups based on their registration.

🎯 Use It: Verify user contact details, enable SMS-based interactions, or trigger follow-ups based on user registration.

✅ Understand It: This trigger activates when your Delphi recommends a product to a user during a conversation.

⚙️ Customize It: Choose a product to recommend from the “Select Product” dropdown, which includes all your available products. Learn how to modify your product offerings in this documentation page.

💡 Example: If your Delphi suggests a coaching package or an exclusive course, this trigger will activate. You can then decide what action this trigger causes, such as following up on their interest, offering a discount, or tracking engagement with recommended products.

🎯 Use It: Follow up on product interest, offer discounts or incentives, or track engagement with recommended products.

✅ Understand It: This trigger activates when a user subscribes to your membership, allowing you to automate responses and follow-ups.

⚙️ Customize It: Choose which membership tier to track by selecting from the “Select Tier” dropdown, which includes all of your available membership tiers. Learn how to modify or add membership options in this documentation page.

💡 Example: If a user joins your premium tier, this trigger will activate. You can then decide what action this trigger causes, such as sending a welcome message, granting exclusive access, or guiding them through onboarding.

🎯 Use It: Send welcome messages, grant exclusive access, offer onboarding guidance, or track new subscribers.

✅ Understand It: This trigger activates when a user completes a payment for a membership or usage.

⚙️ Customize It: Choose to track all transactions, memberships only, or usage-based charges by selecting one of these three options from the “Payments for” dropdown.

💡 Example: If a user pays for a monthly subscription or a one-time service, this trigger will activate. You can then decide what action this trigger causes, such as sending a payment confirmation, granting premium access, or tracking revenue.

🎯 Use It: Send payment confirmations, grant premium access, track revenue, or trigger automated onboarding messages.

✅ Understand It: This trigger activates when a scheduled date and time is reached, triggering a one-time action.

⚙️ Customize It: elect the exact activation date under “Timing” and enter the time in military format (24-hour clock).

💡 Example: If you schedule an announcement for March 15 at 14:00 (2 PM PST), this trigger will activate exactly at that moment. You can then decide what action this trigger causes, such as sending reminders, making announcements, or automating time-sensitive actions.

🎯 Use It: Schedule announcements, send reminders, or automate time-sensitive actions.

✅ Understand It: This trigger activates when a repeating schedule is reached, triggering the action at set intervals (e.g., every 7 days).

⚙️ Customize It: Set the frequency by entering a number between “every” and “days”, and choose the time in military format (24-hour clock). The highest frequency currently allowed is daily. Optionally, set an end date for when the schedule should stop, though this is not required.

💡 Example: If you configure the trigger to activate every 7 days at 10:00 (PST), it will fire once a week at that time. You can then decide what action this trigger causes, such as sending scheduled reminders, automating regular updates, or maintaining ongoing engagement.

🎯 Use It: Automate regular updates, send scheduled reminders, or maintain ongoing engagement.

✅ What It Does: Filters the trigger to activate only for users within specific tagged groups.

⚙️ How to Select: Choose one or multiple tagged groups from the “User Tag” dropdown under “Filters” (default is set to “None,” which includes all users).

💡 Example: If you tag VIP users and set this filter to trigger only for them, it will activate only when a VIP user completes an action, such as making a purchase or reaching a message quota.

❗ Notes:

✅ What It Does: Determines how often the trigger activates when the condition is met.

⚙️ How to Select: Toggle between “First” and “Every” under “Settings” → “Trigger on.”

💡 Example: If you choose “Every”, and the trigger is set to activate when a user completes a purchase, it will fire every time that user makes a purchase. VS. If you choose “First”, the trigger will fire only the first time that user makes a purchase, but not for any future purchases.

🚫 Limitations: Not available for scheduling triggers (On a Specific Date/Time and On a Recurring Schedule) since their activation is predefined.

✅ Understand It: This action allows Delphi (the company) to send you, the Delphi owner, personalized updates or reminders based on specific user interactions. Instead of generic notifications, Delphi crafts tailored messages using context from the trigger event to ensure every response is relevant.

⚙️ Customize It: Select your preferred notification type from the Notification Type dropdown. Options include:

In the box labeled “Describe what should be sent, using the data selected above,” enter a general instruction rather than a specific scripted message. Delphi will generate the right response dynamically, using real-time context from the trigger event. Example:

💡 Example:

🎯 Use It: Stay informed about important user interactions while ensuring that every notification is highly relevant and tailored to the situation. Get alerts for quota limits, payments, or membership sign-ups, and ensure your responses are timely, thoughtful, and specific.

✅ Understand It: This action allows your Delphi to contact a user with a response that is personalized in real-time based on the instructions you provide. Instead of a fixed, scripted message, Delphi dynamically generates a reply using the provided guidance and context from the conversation.

⚙️ Customize It:

💡 Example:

🎯 Use It: Ensure users receive prompt, personalized, and relevant responses that keep conversations flowing naturally and intelligently. Delphi doesn’t just reply—it continues the interaction, maintaining context and engagement.

✅ Understand It: This action allows you to either add or remove a tag from a user based on their interaction. Tags help you segment users, personalize engagement, and track behavior effectively.

⚙️ Customize It:

💡 Example 1: If a user expresses interest in a premium feature, you can select “Add Tag” and apply a “Potential Upsell” tag. This allows you to later target these users with special offers or tailored messages.

💡 Example 2: If a user upgrades from a trial to a paid membership, you can select “Remove Tag” to remove the “Trial User” tag. This ensures they no longer receive trial-specific content and helps maintain accurate user segmentation.

🎯 Use It: Segment users dynamically, trigger personalized follow-ups, and refine user categorization based on their latest interactions.

✅ Understand It: This action allows you to either set or remove a property from a user based on their interaction. Properties store key details about users, such as preferences, activity levels, or status, enabling more personalized experiences and targeted engagement.

⚙️ Customize It:

💡 Example 1: If a user completes an onboarding tutorial, you can select “Set Property” and assign “Onboarding Completed = Yes.” This allows you to track which users have finished onboarding and tailor future interactions accordingly.

💡 Example 2: If a user cancels their subscription, you can select “Remove Property” and delete “Active Subscriber.” This ensures they no longer receive member-specific content or perks.

🎯 Use It: Store valuable user attributes, track key milestones, and refine audience segmentation to create more relevant and meaningful interactions.

✅ Understand It: This action sends a POST request to a specified API with user details, including name, email, phone number, timestamp, and the triggered event.

⚙️ Customize It: 1) Specify the endpoint URL in the “Endpoint URL” box. 2) Configure headers under “Headers.” We automatically create the Content-Type header with the value application/json. You can add one additional header, such as an API token for authorization. Any API token you enter will be encrypted for security and automatically decrypted when sent with the request, ensuring the receiving system can validate that the data is coming from Delphi.

💡 Example: If a user completes a purchase, Delphi can send their name, email, and purchase details to your CRM or analytics tool, ensuring seamless data tracking across platforms.

🎯 Use It: Sync user attributes with external systems, update CRMs, or integrate with analytics tools.

Initiates the action as soon as the trigger occurs.

💡 Example: If a user completes a product recommendation flow with a send message: contact user action, and the delay is set to instant, your Delphi could instantly message them: “I think you’d love [Product Name]! Here’s a link to check it out: [Link]. Let me know if you have any questions!”

Delays the Action for a set time relative to when the trigger occurs. For example, if a user purchases a membership at 8 AM and you set a 2-hour delay before contact, they will receive the notification at 10 AM. Enter a numerical value and select minutes, hours, or days from the dropdown.

💡 Example: If you set a Fixed Delay of 2 hours for a Follow-Up Message after a user abandons their checkout, Delphi will wait exactly 2 hours before sending the message. So, if a user adds an item to their cart at 10 AM but doesn’t complete the purchase, they’ll receive a message at 12 PM, such as: “Still thinking about [Product Name]? Your cart is waiting! Let me know if you need any help.”

Lets your Delphi intelligently determine the best time to execute the action based on conversation history or the instructions you provide in the “Custom Delay: Describe what the delay should be” box. For example, “Message the user an hour after their date” or “Send a birthday message on their birthdate.” Keep the description short—the more concise it is, the easier it will be for your Delphi to understand.

💡 Example: If you set a Custom Delay for a Birthday Message, you might enter: “Send the user a message on their birthday.” Delphi will check their stored birthdate and send a message at the appropriate time, such as: “Happy Birthday, [Name]! 🎉 Wishing you an amazing day. Let me know if I can help with anything special today!”

Test your action by using the “Trigger Occurences” and “Action Occurences” log at the bottom of the sidebar when you click on a trigger or action.

For Send Message actions, responses will vary slightly each time—just as your Delphi’s responses naturally do in regular conversations, even when the same question is asked. Try triggering it multiple times to see the differences.
​

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.

🔹 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.

🛠️ When to Use Each?

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