Email Prefix Configuration

Set up a custom email address like yourname@inbox.stagepulse.com and StagePulse will route any client replies that land there into the right project automatically. The heads-up: this is for inbound email routing, not for sending from a custom domain.

What You Get

Pick a prefix, and StagePulse gives you an address like:

candice@inbox.stagepulse.com

Anything sent to that address is:

• Routed to your business — not visible to other StagePulse users
• AI-analyzed for intent — the system extracts dates (closing date, destage date) and urgency signals from each email
• Attached to a project — if the subject line or email thread matches a project, it's linked automatically
• Summarized into the project's notes — so when you open the project later, you see "Broker confirmed closing moved to May 3rd" without hunting through email

The most common use: broker replies to your extension reminders, contract invitations, or project monitoring emails land in StagePulse and nudge the project notes forward on their own.

Setting Up Your Prefix

1. Go to Settings → Email
2. Type a prefix (letters, numbers, hyphens only)
3. Click Save

The prefix has to be:

• Unique across all StagePulse users
• 3–30 characters long
• Letters, numbers, or hyphens only (no @, ., spaces, underscores)

Pick something professional and memorable since this is what clients will see. Most stagers use their name (candice), business name (noble-design), or a combination.

Using It

Once configured, just start using the address. Share it on invoices, in email signatures, or directly with clients:

• "Best way to reach me about this staging is candice@inbox.stagepulse.com."

Or configure your existing email to auto-forward project-related emails to it — that way you keep your normal inbox for personal mail and StagePulse handles the project chatter.

What Happens With Inbound Email Today

Here's what happens when a broker replies to an email StagePulse sent:

1. The reply lands at your {prefix}@mail.stagepulse.com address (your SES-verified inbound route).
2. StagePulse immediately forwards the raw reply to your real inbox so nothing gets lost — you can reply from your regular mail client as usual.
3. We store the raw email and run AI analysis to pull out closing dates, destage timing, and a short summary.
4. The email is linked back to the matching project (via the original outbound message's Message-ID header).
5. Anyone on the team with notify_inbound_email turned on gets an in-app / push / SMS notification containing the summary, deep-linking to the project.
6. The AI summary is also appended to the project's notes for future reference.

You do not yet get a threaded inbox view inside StagePulse — the forward-to-inbox + notification flow is the way you keep up with replies for now.

Best Practices

• Use a short, business-name-based prefix — it's easier to share verbally
• Put it in your email signature and invoice footer so clients know to use it
• Don't use it for personal mail — you can't easily separate once it's mixed in

What This Isn't

• Not a custom sending domain: outbound emails (invoices, contracts, reminders) send from the StagePulse system address, not from your custom prefix. Custom sending domain is a separate feature roadmap item.
• Not an inbox: no threaded view, no reply UI. Inbound email informs your project context but you don't compose from StagePulse.

Related

• Calendar & Reminders — extension emails go out; broker replies route back via this prefix
• Property Monitoring — broker replies to monitoring alerts route back here
• Contracts & E-Signatures — contract email replies route here