Conduit
Book DemoEnroll in Course
  • Start Guide
  • Setup
    • Workspaces
    • Invite and Manage Members
    • Notifications
    • Mobile
    • Flexible Inboxes
      • Create an Inbox
      • Custom Fields
      • Workflow
  • Channels
    • Property Management System
      • Guesty
      • Track
      • Hostaway
      • BookingSync/Smily
      • Lodgify
      • Hostfully
      • OwnerRez
      • Beds24
      • Add and Remove Listings
    • Email
      • Receiving Emails in Conduit
      • Sending Emails from Conduit
      • Alternate Email Addresses
    • WhatsApp
    • Business Phone Number
      • Port Your Phone Numbers to Conduit
        • OpenPhone
        • Aloware
        • Google Voice
        • Dialpad
        • RingCentral
        • Aircall
        • Grasshopper
        • Zoom Phone
    • Chat Widget
    • Airbnb
      • Standalone
      • With a PMS
  • Using The Inbox
    • Inbox Zero
    • AI Messaging
    • Conversation Tags
    • Labels
    • Notes and Mentions
    • Assignment
    • Saved Replies
    • Insights
  • Building Your AI Agents
    • Road to Autopilot
    • Phase 1: Teaching
      • Sources
      • Required Info
      • Teach as You Go
    • Phase 2: Tuning
      • In the Sandbox
      • In the Inbox
      • Advanced Rules
    • Autopilot
  • Workflows
    • Getting Started
  • Create a Workflow
  • Trigger and Action Libraries
  • AI Agent Injections
  • Integrations
    • Slack
    • Zapier
  • Other
    • Conduit Certification
Powered by GitBook
On this page
  • Overview
  • Workflow
  • Map to Guest
  • Map to a Contact

Was this helpful?

  1. Setup
  2. Flexible Inboxes

Workflow

Map messages to correct inboxes

PreviousCustom FieldsNextProperty Management System

Last updated 1 month ago

Was this helpful?

Overview

When a new inbound message arrives from a connected channel (like Email, SMS, or Widget), the system first checks if the sender’s details (email, phone number, etc.) are already mapped to a contact.

If the details are not mapped, the message will appear in the Connected Channels section.

Workflow

Once mapped, all future communication from this sender (across all channels) will be part of the unified thread under the correct inbox based on their contact type.

If the sender is unmapped, it’s up to you to map the contact. Click on "Map Contact" and you will have the option to:

Map to Guest

When a new message arrives from an unmapped contact, you can map it to a guest if the message pertains to a reservation. Search by the guest's name or reservation ID to locate the correct reservation. Once mapped, the message moves to the Guest Inbox, consolidating all reservation details and communication history with that guest for easy access.

Map to a Contact

If the message is from a general contact (non-guest), you can map it to an existing contact or create a new one. During this process, you’ll select the contact type, which determines the inbox the message will go to (e.g., Homeowner, Contractor). The mapped message will join the contact's unified thread across all channels, ensuring centralized communication.

To unmap a contact detail (like a phone number or email) from an existing contact, go to the contact’s sidebar, locate the mapped detail, and remove it. The unlinked message will then revert to the Connected Channels section, allowing you to remap it as needed.