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

# Form Notifications

> Configure invitations, reminders, and confirmation emails

Form notifications keep contacts informed and drive form completion through invitations, reminders, and confirmations. Effective notification strategies significantly improve response rates.

## Types of Notifications

Forms support three main types of notifications:

<CardGroup cols={3}>
  <Card title="Invitations" icon="paper-plane">
    Initial email when form is sent

    **Purpose:** Introduce the form and provide access
  </Card>

  <Card title="Reminders" icon="clock-rotate-left">
    Automated follow-ups if not completed

    **Purpose:** Encourage completion
  </Card>

  <Card title="Confirmations" icon="circle-check">
    Email after form submission

    **Purpose:** Acknowledge receipt
  </Card>
</CardGroup>

## Invitation Emails

The invitation is the first communication your contact receives about the form. It should be clear, professional, and action-oriented.

### Invitation Components

A well-crafted invitation includes:

1. **Subject Line**
   * Clear and specific
   * Mentions what's needed
   * Creates appropriate urgency
   * Example: "Action Required: Complete Your Onboarding Form"

2. **Opening**
   * Personal greeting
   * Context for why they're receiving this
   * Who it's from

3. **Instructions**
   * What the form is for
   * Estimated time to complete
   * Deadline (if applicable)
   * Why their input matters

4. **Call-to-Action**
   * Clear button or link
   * Action-oriented text
   * Example: "Complete Form Now" or "Get Started"

5. **Additional Information**
   * Support contact
   * Security information
   * Privacy assurance

### Configuring Invitations

Invitations are configured in the Form Template:

```json theme={null}
{
  "invitations": {
    "subject": "Action Required: Complete Your Information",
    "from": {
      "email": "no-reply@company.com",
      "name": "Company Name"
    },
    "body": "Dear {user.given_name},\n\nPlease complete your information form...",
    "template": "custom-invitation-template"
  }
}
```

### Personalization Variables

Use variables to personalize invitation emails:

| Variable             | Description           | Example                                       |
| -------------------- | --------------------- | --------------------------------------------- |
| `{user.given_name}`  | Contact's first name  | "John"                                        |
| `{user.family_name}` | Contact's last name   | "Smith"                                       |
| `{user.email}`       | Contact's email       | "[john@example.com](mailto:john@example.com)" |
| `{reference}`        | Form reference number | "A4K7X9"                                      |
| `{link}`             | Form access link      | Full URL to form                              |
| `{expires_at}`       | Expiration date       | "Dec 31, 2024"                                |

**Example:**

```
Hi {user.given_name},

We need some information from you to complete your onboarding.

This form will take approximately 10 minutes to complete.
Please submit by {expires_at}.

Click here to get started: {link}

Your reference number is {reference} if you need assistance.

Thank you!
```

### Invitation Best Practices

<AccordionGroup>
  <Accordion title="Be clear about what's needed">
    Tell contacts exactly what the form is for and why you need it. Mystery invitations get ignored.
  </Accordion>

  <Accordion title="Set expectations">
    Let contacts know how long the form will take and when you need it completed. This helps them plan.
  </Accordion>

  <Accordion title="Use your branding">
    Customize the from name and email to match your company. This builds trust and improves open rates.
  </Accordion>

  <Accordion title="Make the CTA obvious">
    The link or button to access the form should be impossible to miss. Use action-oriented text.
  </Accordion>

  <Accordion title="Provide support info">
    Include how to get help if they have questions. This reduces confusion and abandonment.
  </Accordion>
</AccordionGroup>

## Reminder Emails

Reminders automatically follow up with contacts who haven't completed the form. They're critical for improving completion rates.

### Why Reminders Matter

**Statistics show:**

* First reminder can increase completion by 20-30%
* Second reminder adds another 10-15%
* Third reminder adds 5-10%
* Beyond three reminders, returns diminish

### Configuring Reminders

```json theme={null}
{
  "invitations": {
    "reminders": {
      "enabled": true,
      "count": 3,
      "interval": 2,
      "unit": "days",
      "subject": "Reminder: Complete Your Form",
      "body": "This is a friendly reminder..."
    }
  }
}
```

**Properties:**

* `enabled`: Turn reminders on/off
* `count`: Number of reminders to send
* `interval`: Time between reminders
* `unit`: "hours", "days", or "weeks"
* `subject`: Email subject line
* `body`: Email content

### Reminder Timing Strategies

<Tabs>
  <Tab title="Standard (2-3-5 days)">
    **Pattern:** Send reminders at 2, 5, and 10 days

    ```json theme={null}
    {
      "count": 3,
      "intervals": [2, 5, 10],
      "unit": "days"
    }
    ```

    **Best for:** Standard forms, 14-day deadline
  </Tab>

  <Tab title="Urgent (1-1-2 days)">
    **Pattern:** Send reminders at 1, 2, and 4 days

    ```json theme={null}
    {
      "count": 3,
      "intervals": [1, 2, 4],
      "unit": "days"
    }
    ```

    **Best for:** Time-sensitive forms, 7-day deadline
  </Tab>

  <Tab title="Relaxed (3-7-14 days)">
    **Pattern:** Send reminders at 3, 10, and 24 days

    ```json theme={null}
    {
      "count": 3,
      "intervals": [3, 10, 24],
      "unit": "days"
    }
    ```

    **Best for:** Non-urgent forms, 30-day deadline
  </Tab>

  <Tab title="Persistent (every 2 days)">
    **Pattern:** Send reminder every 2 days

    ```json theme={null}
    {
      "count": 5,
      "interval": 2,
      "unit": "days"
    }
    ```

    **Best for:** Critical compliance forms
  </Tab>
</Tabs>

### Reminder Content Strategy

Each reminder should be slightly different:

**First Reminder (Gentle)**

```
Hi {user.given_name},

Just a friendly reminder that we're still waiting for your form submission.

It only takes about 10 minutes to complete.

[Complete Form Now]
```

**Second Reminder (Urgency)**

```
Hi {user.given_name},

This form is due in 3 days. Please complete it at your earliest convenience.

If you're having any issues, please let us know.

[Complete Form Now]
```

**Final Reminder (Last Chance)**

```
Hi {user.given_name},

Final reminder: This form expires tomorrow.

Please submit today to avoid delays in your application.

[Complete Form Now - Last Chance]
```

### Reminder Best Practices

<AccordionGroup>
  <Accordion title="Start gentle, increase urgency">
    First reminder is friendly, final reminder creates urgency. Escalate tone gradually.
  </Accordion>

  <Accordion title="Don't over-remind">
    More than 3-4 reminders becomes spam. If they haven't responded by then, try a different approach.
  </Accordion>

  <Accordion title="Time reminders strategically">
    Send reminders when people are likely to act - early week, mid-morning. Avoid Friday evenings.
  </Accordion>

  <Accordion title="Make opt-out easy">
    If contact declines or isn't interested, let them opt out easily. Respect their decision.
  </Accordion>

  <Accordion title="Track reminder effectiveness">
    Monitor which reminders generate responses. Adjust timing and count based on data.
  </Accordion>
</AccordionGroup>

## Confirmation Emails

Send confirmation emails when contacts submit forms. This provides peace of mind and serves as a receipt.

### Configuring Confirmations

Confirmations are set up as notifications in the Form Template:

```json theme={null}
{
  "notifications": [
    {
      "type": "email",
      "to": [{ "role": "creator" }],
      "on": ["responses:completed"],
      "subject": "Thank you for your submission",
      "body": "We received your form..."
    }
  ]
}
```

Or as automations:

```json theme={null}
{
  "automations": [
    {
      "name": "Send confirmation",
      "on": ["responses:completed"],
      "actions": [
        {
          "type": "email",
          "config": {
            "to": "{user.email}",
            "subject": "Submission Confirmed",
            "body": "Thank you, {user.given_name}..."
          }
        }
      ]
    }
  ]
}
```

### Confirmation Components

A good confirmation email includes:

1. **Clear confirmation**
   * "We received your submission"
   * Reference number for tracking

2. **What happens next**
   * Timeline for review
   * Next steps in process
   * When to expect response

3. **Contact information**
   * Who to contact with questions
   * Support email/phone

4. **Receipt/Summary**
   * Summary of what was submitted (optional)
   * Link to view submission (if applicable)

### Confirmation Example

```
Subject: Submission Confirmed - Reference {reference}

Hi {user.given_name},

Thank you for completing your onboarding form!

What's next:
- Our team will review your submission within 2 business days
- You'll receive an email once your account is activated
- If we need any additional information, we'll reach out

Your reference number: {reference}

If you have questions, contact us at support@company.com

Thank you!
Company Name Team
```

## Team Notifications

In addition to contact notifications, notify your team when forms are submitted.

### Configuring Team Notifications

```json theme={null}
{
  "notifications": [
    {
      "type": "email",
      "to": [
        { "email": "team@company.com" },
        { "role": "owner" }
      ],
      "on": ["responses:completed"]
    }
  ]
}
```

**Notification recipients:**

* `{ "email": "specific@email.com" }` - Specific email address
* `{ "role": "owner" }` - Case owner (if form is part of case)
* `{ "role": "creator" }` - Person who created the form

### Team Notification Content

Include relevant information for quick action:

* Who submitted (name, email)
* Form reference number
* Submission timestamp
* Link to view response
* Next action required

## Bounce Handling

Sometimes emails fail to deliver (bounce). Penbox tracks bounces and can notify you.

### Bounce Notifications

```json theme={null}
{
  "notifications": [
    {
      "type": "email",
      "to": [{ "email": "admin@company.com" }],
      "on": ["request_notifications:bounced"]
    }
  ]
}
```

**When to take action on bounces:**

* Verify contact email address
* Try alternative contact method (phone, SMS)
* Update contact information
* Resend with corrected address

## Notification Analytics

Track notification performance to optimize your strategy:

### Key Metrics

* **Open Rate**: Percentage who open invitation
* **Click Rate**: Percentage who click form link
* **Completion Rate**: Percentage who submit form
* **Reminder Effectiveness**: Completion rate per reminder

### Optimization Based on Data

| Metric                | If Low              | Try This                                      |
| --------------------- | ------------------- | --------------------------------------------- |
| **Open Rate**         | Under 40%           | Improve subject lines, verify email addresses |
| **Click Rate**        | Under 60% of opens  | Clearer call-to-action, better email design   |
| **Completion Rate**   | Under 70% of clicks | Simplify form, reduce required fields         |
| **Reminder Response** | Under 10%           | Adjust timing, improve reminder content       |

## Best Practices Summary

<AccordionGroup>
  <Accordion title="Send invitations immediately">
    Send invitations as soon as the form is ready. Delays reduce response rates.
  </Accordion>

  <Accordion title="Use 2-3 reminders">
    This is the sweet spot for most forms. More becomes spam, fewer leaves completions on the table.
  </Accordion>

  <Accordion title="Always send confirmations">
    Confirmations build trust and provide receipts. They take seconds to configure but matter to contacts.
  </Accordion>

  <Accordion title="Personalize everything">
    Use contact name, reference numbers, and specific details. Generic emails get ignored.
  </Accordion>

  <Accordion title="Test email delivery">
    Before launching, send test forms to ensure emails arrive in inbox (not spam).
  </Accordion>

  <Accordion title="Monitor and adjust">
    Track metrics and adjust timing, content, and frequency based on actual performance.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Form Templates" icon="pen-ruler" href="/forms/form-templates">
    Configure notifications in templates
  </Card>

  <Card title="Form Presets" icon="sliders" href="/forms/form-presets">
    Customize invitations per preset
  </Card>

  <Card title="Forms Introduction" icon="circle-info" href="/forms/introduction">
    Back to Forms overview
  </Card>

  <Card title="Form Security" icon="shield-halved" href="/forms/security">
    Secure your forms
  </Card>
</CardGroup>