> ## Documentation Index
> Fetch the complete documentation index at: https://help.hoopai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow AI examples and recipes

> Ready-to-use workflow recipes that combine AI with automation for powerful business outcomes.

The real power of HoopAI's AI features comes alive when you combine them with workflows. Instead of using AI in isolation, you can embed intelligent decision-making into your automated processes -- qualifying leads, routing support tickets, drafting responses, and personalizing outreach without manual intervention.

This page provides six complete, ready-to-use workflow recipes. Each recipe includes the goal, trigger, step-by-step configuration, AI setup, and expected outcome. Use them as-is or adapt them to fit your business.

<Frame caption="Flow-based builder interface for constructing AI-powered workflow automations">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/c_IPTSnbNy09cl5O/images/ai-agents-conversation-ai-flow-based-bui-0-image.png?fit=max&auto=format&n=c_IPTSnbNy09cl5O&q=85&s=c4358a9de876f3cb93c9952c88f78b9c" alt="Flow-based workflow builder showing connected automation steps" width="1114" height="348" data-path="images/ai-agents-conversation-ai-flow-based-bui-0-image.png" />
</Frame>

<Note>
  These recipes use AI actions and the AI decision maker, which consume AI credits. Monitor your usage in **Settings > AI credits**. For details on configuring AI actions, see [Using AI actions in workflows](/ai/workflow-ai/gpt-actions). For branching logic, see [AI decision maker](/ai/workflow-ai/ai-decision-maker).
</Note>

***

## Recipe 1: Lead qualification with AI scoring and sales routing

**Goal:** Automatically score inbound leads based on their form submission data and route high-quality leads to your sales team instantly.

### Trigger

**Form Submitted** -- fires when a contact submits your lead capture form.

### Workflow steps

<Steps>
  <Step title="Trigger: Form submitted">
    Select the specific form (e.g., "Free Consultation Request"). The trigger captures all form field values and contact data.
  </Step>

  <Step title="AI action: Score the lead">
    Add a **GPT-Powered AI Action** with this prompt:

    ```
    You are a lead qualification assistant. Based on the following
    information, assign a lead score from 1-10 and a category
    (Hot, Warm, Cold).

    Contact name: {{contact.name}}
    Email: {{contact.email}}
    Company: {{contact.company_name}}
    Form message: {{form.message}}
    Source: {{contact.source}}

    Respond in this exact format:
    Score: [number]
    Category: [Hot/Warm/Cold]
    Reason: [one sentence explanation]
    ```

    Store the response in a variable called \`lead\_score\_result.
  </Step>

  <Step title="If/Else branch: Route by category">
    Add an **If/Else** condition that checks the \`lead\_score\_result variable:

    * **If** the response contains "Hot" -- proceed to the hot lead path
    * **Else if** the response contains "Warm" -- proceed to the warm lead path
    * **Else** -- proceed to the cold lead path
  </Step>

  <Step title="Hot lead path">
    1. **Add tag:** hot-lead
    2. **Send internal notification** to the sales team via email or Slack: "Hot lead alert: `{{contact.name}}` scored as Hot."
    3. **Send SMS** to the contact: "Thanks for reaching out, `{{contact.first_name}}`! A member of our team will call you within the hour."
    4. **Create task** assigned to the sales manager with a 1-hour deadline
  </Step>

  <Step title="Warm lead path">
    1. **Add tag:** warm-lead
    2. **Send email** with a calendar link to book a discovery call
    3. **Add to nurture campaign** for follow-up in 48 hours if no booking
  </Step>

  <Step title="Cold lead path">
    1. **Add tag:** cold-lead
    2. **Send email** with helpful resources and a soft CTA
    3. **Add to long-term drip sequence**
  </Step>
</Steps>

### Expected outcome

Every lead is scored within seconds of form submission. Hot leads get immediate attention from your sales team, warm leads receive a booking link, and cold leads enter a nurture sequence -- all without manual triage.

***

<Frame caption="Workflow trigger configuration for connecting AI actions to automation sequences">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/pMRqsx_Tmg1Lacem/images/ai-agents-how-to-trigger-a-workflow-with-2-trigger-20workflow.png?fit=max&auto=format&n=pMRqsx_Tmg1Lacem&q=85&s=3274861efd4f75cec4c1c0ad0ce1694c" alt="Trigger workflow configuration interface" width="866" height="645" data-path="images/ai-agents-how-to-trigger-a-workflow-with-2-trigger-20workflow.png" />
</Frame>

***

## Recipe 2: After-hours inquiry with bot handoff and morning follow-up

**Goal:** Handle inquiries that arrive outside business hours with an AI bot, then trigger a personalized follow-up from a team member the next morning.

### Trigger

**Customer Replied** -- fires when a contact sends a message via SMS, email, or web chat.

### Workflow steps

<Steps>
  <Step title="Trigger: Customer replied">
    Set the trigger to fire on any inbound message across all channels.
  </Step>

  <Step title="Condition: Check business hours">
    Add an **If/Else** condition using the **Time of Day** filter. Set your business hours (e.g., Monday-Friday, 9:00 AM-5:00 PM).

    * **If** within business hours -- exit workflow (let your team handle it normally)
    * **Else** -- continue to after-hours path
  </Step>

  <Step title="Enable Conversation AI bot">
    Add an **AI Bot** action that activates your after-hours Conversation AI agent. Configure the bot with instructions to help with basic questions using your knowledge base, collect what the contact needs help with, their preferred contact method, and the best time to reach them.
  </Step>

  <Step title="Wait until business hours">
    Add a **Wait** action set to "Until time of day" -- 9:00 AM the next business day.
  </Step>

  <Step title="AI action: Summarize the conversation">
    Add a **GPT-Powered AI Action** that reads the conversation history and generates a summary in 2-3 bullet points, including what the contact needs and their preferred contact method.
  </Step>

  <Step title="Send internal notification">
    Notify the assigned team member with the AI summary so they can follow up with full context.
  </Step>
</Steps>

### Expected outcome

After-hours inquiries get an immediate, helpful response from your AI bot. The next morning, your team receives a concise summary and can follow up personally -- no inquiry falls through the cracks.

<Frame caption="Conversation AI flow builder showing bot response logic and branching paths">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/c_IPTSnbNy09cl5O/images/ai-agents-conversation-ai-flow-based-bui-3-image.png?fit=max&auto=format&n=c_IPTSnbNy09cl5O&q=85&s=fe04089848003a17fcae86ef94627748" alt="Flow-based builder with conversation AI bot logic nodes" width="1051" height="695" data-path="images/ai-agents-conversation-ai-flow-based-bui-3-image.png" />
</Frame>

***

## Recipe 3: Appointment no-show re-engagement

**Goal:** When a contact misses an appointment, use AI to craft a personalized re-engagement message that acknowledges the missed appointment and offers to reschedule.

### Trigger

**Appointment Status Changed** -- fires when an appointment status changes to "No Show."

### Workflow steps

<Steps>
  <Step title="Trigger: Appointment status changed to No Show">
    Select the **Appointment Status Changed** trigger and filter for the "No Show" status.
  </Step>

  <Step title="Wait 30 minutes">
    Add a **Wait** action for 30 minutes. This gives a buffer in case the status was set prematurely.
  </Step>

  <Step title="AI action: Draft re-engagement message">
    Add a **GPT-Powered AI Action** that drafts a friendly, non-judgmental SMS message. The prompt should instruct the AI to acknowledge the missed appointment without blame, express understanding, and offer a direct link to reschedule. Keep it under 160 characters if possible.
  </Step>

  <Step title="Send SMS">
    Send an SMS using the AI-generated message as the body. Append your calendar booking link.
  </Step>

  <Step title="Wait 24 hours, then follow up">
    If no reply after 24 hours, send a second follow-up via email with additional rebooking options and a direct phone number to call.
  </Step>
</Steps>

### Expected outcome

Missed appointments get a timely, empathetic follow-up that feels personal rather than automated. Rebooking rates improve because the message is tailored to the specific appointment and contact.

***

## Recipe 4: Review response with AI draft and human approval

**Goal:** When a new review comes in, have AI draft a response for your team to review and approve before posting.

### Trigger

**Review Received** -- fires when a new Google or Facebook review is detected.

### Workflow steps

<Steps>
  <Step title="Trigger: Review received">
    Set the trigger to fire on all new reviews, regardless of star rating.
  </Step>

  <Step title="If/Else: Check star rating">
    Branch based on the review rating:

    * **5 stars** -- Positive response path
    * **3-4 stars** -- Neutral response path
    * **1-2 stars** -- Negative response path
  </Step>

  <Step title="AI action: Draft the response">
    Each branch gets its own AI action with a tailored prompt. For negative reviews, instruct the AI to thank the reviewer for their feedback, apologize for the experience without admitting fault, offer to resolve the issue offline, include a support email, keep it under 100 words, and avoid being defensive or dismissive.

    <Tip>
      Use a dedicated Slack channel like #review-responses so your team can quickly approve, edit, and post responses throughout the day.
    </Tip>
  </Step>

  <Step title="Send for approval">
    Send an **Internal Notification** (email or Slack) to your team with the original review text and rating, the AI-drafted response, and a link to the review platform to post the response.
  </Step>
</Steps>

### Expected outcome

Every review gets a thoughtful, on-brand draft response within minutes. Your team reviews and posts it, ensuring quality control while saving 80% of the time it takes to write responses from scratch.

<Frame caption="Update Conversation AI bot workflow action for managing bot behavior in automations">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/Eqk2wLxdN8J-FylJ/images/automation-update-conversation-ai-bot-and-0-image.png?fit=max&auto=format&n=Eqk2wLxdN8J-FylJ&q=85&s=c09953ebe9176eda8d0101d9df5467dc" alt="Workflow action to update conversation AI bot settings" width="1338" height="787" data-path="images/automation-update-conversation-ai-bot-and-0-image.png" />
</Frame>

***

<Frame caption="Workflow builder interface showing the auto follow-up action configuration">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/XJ0T_i1eGn0rhbtc/images/ai-agents-auto-followup-action-in-conver-12-actions.png?fit=max&auto=format&n=XJ0T_i1eGn0rhbtc&q=85&s=f430ab4d116ba51a31860db687b4882d" alt="Auto follow-up workflow builder with action steps" width="1349" height="699" data-path="images/ai-agents-auto-followup-action-in-conver-12-actions.png" />
</Frame>

***

## Recipe 5: New contact AI welcome with drip sequence

**Goal:** Send a personalized AI-generated welcome message to new contacts and enroll them in a targeted drip sequence based on their interests.

### Trigger

**Contact Created** -- fires when a new contact is added to HoopAI.

### Workflow steps

<Steps>
  <Step title="Trigger: Contact created">
    Optionally add a filter for specific sources (e.g., only contacts from web forms, not manual imports).
  </Step>

  <Step title="Wait 2 minutes">
    A short delay ensures all contact data has fully synced before the AI processes it.
  </Step>

  <Step title="AI action: Generate welcome message">
    Use a GPT-Powered AI Action to write a personalized welcome SMS. The prompt should instruct the AI to welcome the contact warmly, reference how they found you (if source data is available), ask one qualifying question about what they are looking for, be conversational (not corporate), and stay under 300 characters.
  </Step>

  <Step title="Send welcome SMS">
    Send the AI-generated welcome message via SMS.
  </Step>

  <Step title="AI action: Classify interest">
    When the contact replies, use an AI action to classify their primary interest into one of your predefined categories (e.g., Service A, Service B, Service C, General Inquiry). Instruct the AI to respond with only the category name.
  </Step>

  <Step title="If/Else: Route to drip sequence">
    Branch on the classification result and add the contact to the appropriate drip campaign for their interest category.
  </Step>
</Steps>

### Expected outcome

New contacts receive a personalized welcome within minutes. Their first reply is automatically classified and used to enroll them in the most relevant nurture sequence, ensuring they receive content that matches their interests from day one.

***

<Frame caption="Adding the AI Summarize action to condense conversation history into key points">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/hMXZiYP_XWldArYH/images/help-center-workflow-ai-summarize-add-action.png?fit=max&auto=format&n=hMXZiYP_XWldArYH&q=85&s=c8ceeb6b08207c19152c50dafac3dd2e" alt="AI Summarize action being added to a workflow" width="1337" height="791" data-path="images/help-center-workflow-ai-summarize-add-action.png" />
</Frame>

## Recipe 6: Support ticket AI classification and team routing

**Goal:** Automatically classify incoming support requests by urgency and topic, then route them to the correct team member with full context.

### Trigger

**Customer Replied** -- fires when a contact sends a message tagged as a support request (or from a support-specific channel).

### Workflow steps

<Steps>
  <Step title="Trigger: Customer replied">
    Filter to messages from your support channel, support email, or contacts with a "support-request" tag.
  </Step>

  <Step title="AI action: Classify the ticket">
    Use a GPT-Powered AI Action to classify the support message. The prompt should instruct the AI to analyze the message and respond with an urgency level (Low, Medium, High, or Critical), a category (Billing, Technical, Account, Feature Request, or Other), a one-sentence summary, and a brief suggested action.
  </Step>

  <Step title="If/Else: Route by urgency">
    Branch on the classification result:

    * **Critical** -- Immediate notification to team lead plus auto-assign
    * **High** -- Assign to next available senior support agent
    * **Medium** -- Add to support queue with standard SLA
    * **Low** -- Auto-respond with knowledge base article if relevant, queue for batch review
  </Step>

  <Step title="Critical path actions">
    1. **Send internal notification** to the support team lead with the full classification
    2. **Create task** with a 1-hour deadline
    3. **Send SMS to contact:** "We've received your message and a senior team member is reviewing it now. We'll get back to you shortly."
    4. **Add tag:** critical-support
  </Step>

  <Step title="Low urgency path: AI auto-response">
    For low-urgency tickets, add a second AI action that drafts a helpful response using the knowledge base. If the AI cannot answer confidently, it should say a team member will follow up. Send the response via the same channel the contact used.
  </Step>
</Steps>

### Expected outcome

Every support request is classified within seconds. Critical issues get immediate human attention, while routine questions receive instant AI-powered answers. Your team focuses their energy where it matters most.

***

<Frame caption="Conversation AI flow builder with multiple connected nodes and decision paths">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/c_IPTSnbNy09cl5O/images/ai-agents-conversation-ai-flow-based-bui-5-image.png?fit=max&auto=format&n=c_IPTSnbNy09cl5O&q=85&s=66394b8ce97cf58e8e7b985e4000f439" alt="Advanced flow-based builder showing complex workflow with AI bot integration" width="1377" height="790" data-path="images/ai-agents-conversation-ai-flow-based-bui-5-image.png" />
</Frame>

<Frame caption="Complete workflow example showing AI Intent Detection routing messages to different paths">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/hMXZiYP_XWldArYH/images/help-center-workflow-ai-intent-detection-workflow-example.png?fit=max&auto=format&n=hMXZiYP_XWldArYH&q=85&s=c7f3fd4e06c9994849d8d11de71e5008" alt="Intent detection workflow with branching paths based on AI classification" width="931" height="459" data-path="images/help-center-workflow-ai-intent-detection-workflow-example.png" />
</Frame>

<Frame caption="Configuring source and target languages for AI-powered translation in workflows">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/hMXZiYP_XWldArYH/images/help-center-workflow-ai-translate-source-target-languages.png?fit=max&auto=format&n=hMXZiYP_XWldArYH&q=85&s=fb43775920ce352fe3a820824fec09f4" alt="Language selection for the AI Translate workflow action" width="688" height="723" data-path="images/help-center-workflow-ai-translate-source-target-languages.png" />
</Frame>

<Frame caption="Common GPT action use cases including summarization, translation, sentiment analysis, and FAQ responses">
  <img src="https://mintcdn.com/hoopai-84ec0cdc/hMXZiYP_XWldArYH/images/help-center-workflow-ai-gpt-usage-cases.png?fit=max&auto=format&n=hMXZiYP_XWldArYH&q=85&s=363028615d19e0a8fa96a6121c3d721b" alt="Overview of GPT action types and usage scenarios" width="1333" height="956" data-path="images/help-center-workflow-ai-gpt-usage-cases.png" />
</Frame>

## Customizing these recipes

Each recipe is a starting point. Here are common ways to adapt them:

* **Swap channels** -- Replace SMS with email, WhatsApp, or web chat depending on your audience
* **Adjust timing** -- Change wait durations to match your business cadence
* **Add conditions** -- Layer in additional If/Else branches for more granular routing
* **Combine recipes** -- Chain multiple recipes together (e.g., lead qualification followed by welcome followed by drip)
* **Refine prompts** -- Iterate on AI prompts based on real conversation data to improve accuracy

<Warning>
  Always test workflows with sample contacts before activating them for your full audience. Use the workflow test mode to verify each step produces the expected output.
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="AI actions in workflows" icon="bolt" href="/ai/workflow-ai/gpt-actions">
    Deep dive into configuring GPT-powered AI actions for your workflows.
  </Card>

  <Card title="AI decision maker" icon="code-branch" href="/ai/workflow-ai/ai-decision-maker">
    Use AI to make intelligent branching decisions in your workflows.
  </Card>

  <Card title="Connecting bots to workflows" icon="link" href="/ai/workflow-ai/connecting-bots">
    Learn how to trigger and control Conversation AI bots from within workflows.
  </Card>

  <Card title="Prompt engineering overview" icon="pen" href="/ai/prompt-engineering/overview">
    Write better prompts to get more accurate and useful AI outputs.
  </Card>
</CardGroup>
