Every email address and phone number in one place
The Access Points page lists every address and number your account can be reached on and what each one is wired to. You can also reserve an email address before you are ready to use it, so nobody else claims it first.
QuickCasa now has one page that answers the question "what can reach us, and where does it go". Access Points, under Settings in the sidebar, is a company-wide roll-up of every email address and phone number in your account, so you no longer have to open each flow one at a time to find out.
The three kinds of address
Email addresses split into three lists, because they do different jobs:
- Intake sources are addresses leads write to. These route conversations, so an address can only be an intake source on one flow.
- Reserved are addresses held for your account but not wired to anything yet.
- Recipients are addresses QuickCasa sends to rather than listens on: off-work forwarding, business goal notifications, tour and application contacts, maintenance request recipients. The same address can legitimately appear on many flows here.
Every Used In entry is a link that opens the flow or switchboard it belongs to. The search box matches on the address, the note left against it and the property name, so you can find a row from whichever end you happen to remember. Addresses stored as linked-data variables are resolved first, so you see the real address rather than the variable name.
Holding an address before you need it
Intake addresses are first come, first served across all of QuickCasa, which means an address you are planning to launch with can be taken by somebody else while you get ready. Reserve Address holds one for your account, with an optional note about what it is for that your team sees in the Held For column.
A reservation is a hold, not a channel. Nothing routes to a reserved address, and mail sent to it is not received. It starts working once you add it to a flow as an intake source. Reservations do not expire, and releasing one puts the address back in the pool.
Two flows can no longer claim the same address
Saving a flow with an email address that something else already holds is refused, with the reason shown. If another of your own flows has it, the message names that flow so you can go and remove it there first. If another account has it, you are told only that the address is taken, never whose it is. Casing and stray spaces do not let a duplicate through.
Conflicts that predate this check are listed on the Account Health page, with links to every flow claiming each address.
What's next
Want this on
your portfolio?
Book a demo to see what's live today, or browse every update we've shipped.