Three inboxes, three permissions
leads.view and support.view are granted independently, so a salesperson never sees support tickets by accident, and vice versa, even though both flow through the exact same underlying pipeline.
Leads, Support & Feedback
Every message sorted before it lands.
Sales opportunities, support requests and feedback flow into three separate inboxes, not one that everyone digs through, each gated by its own permission and each tracking who read what, and when.
- 3 separate inboxes Sales, support and feedback each get their own permission, their own counter and their own search
- Up to 50 custom fields Every organization defines its own extra fields without anyone touching the database schema
- Read, tracked, reversible Every entry records who read it first and when, and can be marked unread again to hand it to someone else
Four pieces of a message landing correctly.
Each one solves a different part of getting a message to the right person, in the right shape.
Any field, without a migration
A message always requires a name and at least an email or a phone, but extra fields carry whatever else an organization wants to ask, group size, product of interest, campaign source, without ever needing a schema change.
Unread counts, right in the menu
Each inbox shows how many entries are still unread directly in the admin navigation, and search reaches into the message body and every custom field, not just the name and contact info.
Export without losing the custom fields
CSV export respects whatever search or filter is active and keeps custom fields intact as a single JSON column, so the format stays stable even as an organization's forms keep changing.
An AI concierge answers before a human has to
The storefront's chat checks real product and order data before it says anything, never a guess, and hands the conversation to a human the moment it hits a question it genuinely cannot answer on its own.
Slack hears about it too
Sales, leads, support and feedback each route to their own Slack channel if an organization connects one, with a button straight back to the exact entry, so nobody has to keep the inbox open just to notice something new.
How it resolves
How a message finds the right inbox
Five steps, from the moment a form gets submitted to the moment someone on the team acts on it.
- 1
The message arrives through its own endpoint
Leads, support requests and feedback each post to their own endpoint, sharing the same validation and the same per-organization isolation, but never mixing into one generic inbox.
- 2
A reference gets generated, nothing personal echoed back
The response confirms receipt with an opaque reference and a timestamp, and deliberately never repeats back the name, email or message that was just submitted.
- 3
It lands in exactly one inbox
The type on the submission, sales, support or feedback, routes it straight to its matching inbox and its matching permission, with no manual sorting step for anyone.
- 4
Opening it stamps who and when
The first time someone opens an entry, that moment and that person get recorded automatically, so a team always knows what has actually been looked at.
- 5
It can go back to unread, on purpose
Marking something unread again is a normal, supported action, for handing an entry to someone else or flagging it to revisit later, not an edge case the interface fights against.
The API, as it is
Sending a lead without touching the backend
A name, an email or phone, an optional message, and extra fields defined entirely by the organization. The response confirms receipt without echoing anything personal back.
POST /api/v1/organizations/{organization}/leads
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
{
"request": {
"name": "Marco Belli",
"email": "[email protected]",
"message": "Interested in a group booking for October",
"extra_fields": {
"group_size": 24,
"product_of_interest": "city-food-tour"
}
},
"response": {
"data": {
"reference": "01J8X8QK6Z9K2R3W4M5N6P7Q8R",
"type": "sales",
"received_at": "2026-08-14T18:15:00Z"
}
}
}201 Lead received
The detail almost nobody explains
A lead can carry data no one designed a column for
Extra fields accept up to 50 top-level keys, 16 levels of nesting and 64KB of JSON, so a form asking about group size today can start asking about a preferred language next month without anyone touching the database. The limits exist so one aggressive integration can't quietly turn a lead submission into an unbounded upload.
Frequently asked questions
No. leads.view and support.view are two separate permissions on two separate inboxes. A role can be granted one, both, or neither, and there's no shared "contacts" view where they'd blend together.
Yes, through extra fields, a JSON object an organization defines freely, up to 50 fields, without ever needing a change to the database itself.
An opaque reference and the type and timestamp of their submission, nothing more. Their own name, email or message are never echoed back in the response.
No. They export as a single JSON column, so the file stays a stable, predictable format even as an organization's forms and questions keep evolving.
No, it's a completely normal action, meant for handing an entry to someone else on the team or flagging it to come back to, not something the system treats as unusual.
Within a limit an organization sets, yes, and only after the visitor confirms their own email. Anything above that limit, or anything it is not confident about, gets handed to a human instead of guessed at.
No. Slack is entirely optional. Connect it and choose which of the nine notification types land in which channel; leave it disconnected and the three inboxes work exactly the same from the dashboard.
More bookings. More channels. The same calm.
Tiqory keeps availability, pricing, payments and access working together as your operation grows. Tell us where you are headed; we’ll show you how to get there without starting over.