Sales inquiries
Platform-admin queue for triaging sales leads — Talk-to-Sales submissions from the website, and enablement requests from customer organizations — from New to Closed.
Sales Inquiries is the platform-admin triage queue for every sales lead. Each one lands here as a row you can open, read in full, and work through a simple lifecycle. The page is admin-only; the management API behind it is gated to the admin role.
Where leads come from#
The Type column says which door a lead came through, and the filter above the table narrows the list to one of them. The list is paged on the server, newest first.
| Type | Comes from | What you can trust |
|---|---|---|
| Sales | The public Contact page (/contact, topic Plans and pricing) and the Talk to Sales page (/contact-sales) |
What the prospect typed — the form is public, so treat name, email and company as claims |
| Early access | The retired enterprise early-access application. Historical rows only — nothing new is created with this type | Same as Sales. New partner applications go to Partner requests, not here |
| Enablement | Request an enablement session on the Security Academy page, sent by a signed-in organization administrator | Name, email, company and plan come from the administrator's account, not from a form — the request is exactly who it says it is |
Every new lead of any type is also emailed to the sales mailbox (leads@pulsvault.com), with the details and a link back to this screen — so a lead is noticed without anyone watching the list. A mail outage never loses a lead: it is saved first and the email follows.
An enablement request can only be created by an administrator of an existing organization (anyone holding the organization's configuration permission). The public forms cannot create one.
What a lead contains#
| Field | Notes |
|---|---|
| Lead | Name and email; open the lead for a mailto link |
| Company | The organization's name — for an enablement request, its name on file |
| Request | The first lines of what they wrote, so you can scan the list without opening each lead; hover for the whole message, or open the lead |
| Type | Sales, Early access or Enablement; enablement requests also show what was asked for — Instructor-led team training or Security maturity assessment |
| Plan | Wants … — the plan a public prospect is interested in. On … — the organization's own plan (its owner's subscription) when it asked |
| Status | Current lifecycle state (see below) |
| Date | When the lead was submitted |
Refresh re-fetches the current page on demand.
Working a lead#
- Open Sales Inquiries and filter to the type you are working — for example Enablement for existing customers.
- Select Open on a New lead. The side panel shows the full message, the contact details and, for an enablement request, the organization's ID.
- Set the status to In Review and add an internal note, then Save.
- Reply from the email link, then mark the lead Contacted with a note of what was agreed.
- When the conversation concludes, set it to Closed.
Triage lifecycle#
| Status | Meaning |
|---|---|
| New | Just submitted; nobody has looked at it yet |
| In Review | Someone is qualifying the lead |
| Contacted | The prospect or customer has been reached |
| Closed | Done — won, lost, or not a fit |
Internal notes are for staff only and are never shown to the customer. Use them for who called whom, what was agreed and the next step. Every status or note change is recorded in the platform audit trail.
If another admin saves the same lead while you are editing it, your save is refused rather than overwriting theirs: the panel loads their version, keeps your draft on screen, and you save again once you have reconciled the two. Closing the panel with unsaved changes asks before discarding them.
Statuses and notes are the only shared signal between admins — update them as you go so a second admin doesn't double-contact the same prospect.
Limits#
To keep the queue free of noise, the public forms accept up to 20 submissions per network in 24 hours, and an organization can send up to five enablement requests in 24 hours. An organization whose subscription has lapsed into read-only can still send one — asking for help is exactly what that customer should be able to do.
Related#
- App configuration — the subscription packs and pricing the prospect saw
- Enterprise contracts — negotiated terms for a prospect who agreed a deal
- Plans & subscription — how customers subscribe once the deal closes