Show a Message

Display custom messages and instructions to users through action buttons

The "Show a Message" action button displays a custom message to users in a modal dialog. It's perfect for providing additional instructions, important information, or detailed explanations without cluttering your interface. The message supports full markdown formatting, allowing you to include formatted text, links, lists, and more.

When to Use Show a Message

Use the Show a Message action when you want to:

• Provide instructions: Explain complex processes or required steps before users proceed

• Display important information: Show critical details, warnings, or policies

• Hide details to reduce clutter: Keep interfaces clean by revealing information only when needed

• Guide users through processes: Offer contextual help at key decision points

• Show terms and conditions: Display agreements or policies users should review

• Provide reference information: Share lookup tables, formulas, or quick reference guides

Setting Up a Show a Message Action

Step 1: Create the Action Button

1. In build mode, navigate to the record page or view where you want the button

2. Click the "+" button in the Action Buttons section

3. Click the edit icon to configure the button

Step 2: Configure Button Appearance

• Button Text: The label users see (e.g., "View Instructions", "Read More", "Help")

• Appearance: Choose a color scheme (Default, Success, Warning, Danger)

• Icon: Optionally add an icon (e.g., info icon, question mark, document icon)

• Button Tooltip: Add hover text to explain what the button does

Step 3: Configure the Action

1. What Should Happen: Select Show a Message

2. Modal Title: Set the title that appears at the top of the message modal

3. Message Content: Write your message using markdown formatting

4. Confirm Button Text: Customize the button text (default is "Confirm", but you can change it to "Got it", "I Understand", "Close", etc.)

Common Use Cases

1. Process Instructions

Scenario: Guide users through a multi-step approval process

Button Configuration:

• Button Text: "How to Approve"

• Icon: Info icon

• Modal Title: "Approval Process Instructions"

• Confirm Button: "Got it"

Message:

## Approval Workflow

Follow these steps to approve this request:

1. **Review the request details** below carefully
2. **Check budget availability** in the Finance dashboard
3. **Verify approver authority** - requests over $10,000 require director approval
4. Click the **Approve** button if all criteria are met

### Important Notes

- Approvals are **final** and cannot be undone
- The requestor will be notified immediately upon approval
- All approvals are logged for audit purposes

Need help? Contact [[email protected]](mailto:[email protected])

2. Important Policy Information

Scenario: Display company return policy before processing a return

Button Configuration:

• Button Text: "View Return Policy"

• Appearance: Warning (amber)

• Icon: Document icon

• Modal Title: "Return & Refund Policy"

• Confirm Button: "I Understand"

Message:

## Return Eligibility

Items can be returned within **30 days** of purchase if they meet these conditions:

- ✅ Item is in original condition
- ✅ Original packaging included
- ✅ Receipt or proof of purchase provided
- ❌ Custom or personalized items **cannot** be returned

## Refund Process

1. Refunds are processed within 5-7 business days
2. Original payment method will be credited
3. Shipping costs are non-refundable
4. Return shipping is the customer's responsibility

**Questions?** Call customer service at 1-800-555-0123

3. Calculation Reference

Scenario: Show how a complex calculation is performed

Button Configuration:

• Button Text: "How is this calculated?"

• Icon: Calculator icon

• Modal Title: "Commission Calculation Breakdown"

• Confirm Button: "Close"

Message:

## Commission Formula

Your commission is calculated as follows:

**Base Commission** = Sales Amount × Base Rate ({{record.base_rate}}%)

**Bonus Tiers:**

- Sales < $50,000: No bonus
- Sales $50,000 - $99,999: +2% bonus
- Sales $100,000+: +5% bonus

**Final Formula:**

Total Commission = Base Commission + (Base Commission × Bonus %)

### Example
If you sold **$75,000** at a **10% base rate**:
- Base: $75,000 × 10% = $7,500
- Bonus: $7,500 × 2% = $150
- **Total Commission**: $7,650

4. Data Collection Guidelines

Scenario: Explain data requirements before users fill out a form

Button Configuration:

• Button Text: "📋 Data Entry Guidelines"

• Modal Title: "How to Complete This Form"

• Confirm Button: "Start Entry"

Message:

## Required Information

Before completing this form, please have the following ready:

### Customer Details

- Full legal name (as it appears on ID)
- Current mailing address
- Valid email address
- Phone number

### Account Information

- Account number (format: XXX-XXXXX-XX)
- Service start date
- Billing preference

## Formatting Rules

- **Dates**: Use MM/DD/YYYY format
- **Phone numbers**: Include area code (XXX) XXX-XXXX
- **Currency**: Enter numbers only, no $ or commas

> **💡 Tip**: Save your work frequently using the "Save Draft" button below

5. Feature Explanation

Scenario: Explain a complex feature before users enable it

Button Configuration:

• Button Text: "What does this do?"

• Appearance: Default

• Icon: Question mark icon

• Modal Title: "Auto-Assignment Feature"

• Confirm Button: "Got it"

Message:

## How Auto-Assignment Works

When enabled, new tickets will be **automatically assigned** to available team members based on:

1. **Workload balancing** - Team members with fewer active tickets receive priority
2. **Skill matching** - Tickets are matched to members with relevant expertise
3. **Availability status** - Only "Available" team members receive assignments

### Assignment Algorithm

- New tickets are checked every **5 minutes**
- Maximum of **10 active tickets** per team member
- "Out of office" members are automatically skipped

### You Can Still:

- Manually reassign tickets at any time
- Override auto-assignments
- Disable the feature temporarily

**Note**: This setting applies to your entire team.

6. Troubleshooting Help

Scenario: Provide troubleshooting steps for common issues

Button Configuration:

• Button Text: "Troubleshoot"

• Appearance: Warning

• Icon: Tools icon

• Modal Title: "Connection Issues - Troubleshooting"

• Confirm Button: "I'll try this"

Message:

## Quick Fixes for Connection Issues

Try these steps in order:

### Step 1: Check Your Connection

1. Verify you're connected to the internet
2. Try accessing other websites
3. Check if you're on VPN (may need to disconnect)

### Step 2: Clear Cache

1. Press `Ctrl + Shift + Delete` (Windows) or `Cmd + Shift + Delete` (Mac)
2. Select "Cached images and files"
3. Click "Clear data"
4. Refresh this page

### Step 3: Try Different Browser

- Chrome (recommended)
- Firefox
- Safari
- Edge

### Still Not Working?

Contact IT Support with this information:

- Your user ID: {{user.id}}
- Error code (if shown): **\_\_\_**
- Time of error: **\_\_\_**

**Emergency**: Call [phone] ext. 4

7. Terms and Conditions

Scenario: Display terms before a critical action

Button Configuration:

• Button Text: "Read Terms Before Deleting"

• Appearance: Danger (red)

• Icon: Warning icon

• Modal Title: "⚠️ Data Deletion Terms"

• Confirm Button: "I Understand"

Message:

## Important: Data Deletion is Permanent

By proceeding with deletion, you acknowledge:

### What Will Be Deleted

- ❌ All record data and history
- ❌ Associated files and attachments
- ❌ Related comments and notes
- ❌ Audit trail for this record

### What Cannot Be Recovered

**This action is PERMANENT and IRREVERSIBLE.**

- No backups are retained after deletion
- Customer support **cannot** restore deleted data
- Export data before deleting if you need a record

### Legal Requirements

- Deletion complies with GDPR "Right to be Forgotten"
- Some data may be retained for legal/audit purposes (90 days)
- Deletion is logged with user ID and timestamp

> **⚠️ WARNING**: Only proceed if you're absolutely certain you want to delete this data permanently.

**Last chance**: Consider archiving instead of deleting.

Tips for Effective Messages

1. Keep It Scannable

• Use headings and subheadings to organize content

• Break up large blocks of text with bullet points

• Use bold and italic for emphasis sparingly

• Add spacing between sections

2. Use Visual Cues

• ✅ ❌ ⚠️ 💡 📋 Emojis can make messages more engaging

• Bold important warnings or key information

• Use code formatting for technical terms or values

• Add > blockquotes for important notes

3. Make It Actionable

• Tell users exactly what to do next

• Include relevant links or contact information

• Reference specific buttons or fields they'll interact with

• Provide examples when helpful

4. Consider Context

• Keep messages concise for simple actions

• Provide comprehensive details for complex processes

• Match the tone to the action (serious for destructive actions, friendly for help)

• Use dynamic field values with {{record.field_name}} or {{user.property}}

5. Customize the Confirm Button

Choose button text that fits the context:

• "Got it" - Casual acknowledgment

• "I Understand" - Important information

• "Close" - Simple dismissal

• "Let's Go" - Starting a process

• "Proceed" - Moving forward

• "Cancel" - Backing out

Dynamic Content in Messages

You can include dynamic field values in your messages using tokens:

Record fields: {{record.field_name}}

Your order #{{record.order_number}} will ship to:
{{record.shipping_address}}

User properties: {{user.property}}

Welcome {{user.name}}! Your role is: {{user.role}}

Related record fields: {{record.relationship.field}}

Customer: {{record.customer.company_name}}
Contact: {{record.customer.email}}

Best Practices

Do:

• ✅ Keep messages focused on one topic or purpose

• ✅ Use clear, simple language

• ✅ Test your markdown formatting before publishing

• ✅ Include contact information for follow-up questions

• ✅ Update messages when processes change

• ✅ Use appropriate tone for the context

Don't:

• ❌ Include too much information - keep it digestible

• ❌ Use Show a Message for actions that modify data (use Update/Create actions instead)

• ❌ Forget to update messages when workflows change

• ❌ Make messages too formal or robotic

• ❌ Rely on color alone to convey meaning (use words too)

• ❌ Include sensitive data like passwords or API keys

Combining with Other Actions

Show a Message can be combined with other action button actions:

Example: Guided Multi-Step Process

1. Show a Message: Display instructions for the process

2. Update Record: User fills out a form to update fields

3. Show a Message: Confirm completion and explain next steps

Example: Informed Decision

1. Show a Message: Explain what an approval means

2. Update Record: User updates status to "Approved"

3. Run Workflow: Trigger notification workflows

Troubleshooting

Message Not Displaying Correctly

• Check your markdown syntax (missing closing tags, incorrect formatting)

• Preview in a markdown editor before adding to Noloco

• Ensure links are properly formatted with [text](url)

Dynamic Fields Not Showing

• Verify field names match exactly (case-sensitive)

• Check that the field exists on the record

• Use {{record.field_name}} for current record fields

Button Not Appearing

• Check action button visibility rules

• Verify the button hasn't been hidden in settings

• Ensure you've published your changes

Markdown Not Rendering

• Some advanced markdown features may not be supported

• Stick to basic formatting: headers, bold, italic, lists, links

• Test with simple formatting first, then add complexity