These four pages talk to InspectSync, not to your own company. Your customers' support tickets live under Operations › Support; this section is for the things you want from the people who build the product. Each page is a short form with a Submit button and a thank-you page, and everything you send arrives with your account already identified, so there is nothing to explain twice.
Feature Suggestions
Open Feature SuggestionsWho it is for
Anyone who has thought "I wish it could..." while doing their job.
Without it
Good ideas are said out loud once, to a colleague, and lost. The ones that reach the vendor arrive as a line in an email with no context about which screen or how often.
What it shows
One form: a Title, the Module it relates to (Home, Jobs, Quotes, Customers, CRM, Contracts, Billing, Operations, Analytics, or General / Platform-wide), a Priority (Critical, Important, Nice to Have), a Description, a Use Case asking how the feature would help your workflow, and Attachments.
What it is worth
- The idea is captured where it happened. Thirty seconds in the app instead of an email later that never gets written.
- The use case travels with it. "How would this help your workflow" is the part that turns a wish into something buildable.
- Priority from the person who feels it. Critical, Important or Nice to Have, set by you rather than guessed by us.
Pays for itself the first release that includes something one of your people asked for here.
Feedback
Open FeedbackWho it is for
Anyone with something to say that is not a feature and not a bug.
Without it
"This screen is confusing" or "this saved us an hour" has nowhere to go, so the vendor hears only about breakage and never about what works or what merely annoys.
What it shows
The simplest form in the section: a Title, a Description of your experience, and Attachments.
What it is worth
- No category to pick. If it does not fit the other three forms, it fits here.
- Praise counts too. Knowing what works protects it from being changed.
- A screenshot says it faster. Attach one and skip the description.
Pays for itself the first time a confusing screen is reworded because someone here said it was confusing.
Report a Bug
Open Report a BugWho it is for
Anyone who just watched the application do the wrong thing.
Without it
A bug is worked around, mentioned at the next meeting, and half-remembered by the time it reaches anyone who can fix it. The screenshot that would have explained it was never taken.
What it shows
A Title, the Module where it happened, a Description prompted with "What happened? What were you trying to do? What did you expect to happen?", and Screenshots / Attachments.
What it is worth
- Reported while it is on screen. The screenshot and the steps are fresh.
- The three questions that matter. What happened, what you were doing, what you expected. That is a reproducible report.
- Filed against the right module. It lands with the people who own that screen.
Pays for itself the first bug fixed from a report that took two minutes to file.
Concierge Requests
Open Concierge RequestsWho it is for
The person who owns the account's setup and would rather hand the tedious parts to us.
Without it
Loading a supplier's catalog, wiring up an API feed or reconfiguring a workflow is an afternoon of someone's time, done once and done nervously.
What it shows
A grid of the requests the account has submitted: Type, Description, Status, Submitted and Files. A New Concierge Request modal asks for a Request Type (API Catalog Request, File Catalog Update or Configuration Assistance), a Description and Attachments.
What it is worth
- Setup work done by the people who do it daily. A catalog update or an API connection is routine for us.
- A record with a status. Unlike an email, the request stays on the grid until it is done.
- Files travel with the request. Attach the supplier spreadsheet and skip the follow-up thread.
Pays for itself the first supplier price list loaded by attaching it here instead of keying it in.
Where to go next
- Support tickets from your own customers are a different thing entirely and live under Operations › Support.
- Catalogs that a concierge request loads or updates are managed under Admin › Catalogs.
- Your own settings, name and time zone are on My Profile, opened from the avatar menu in the top bar.
Good to know
- These pages leave the tenant. Suggestions, feedback, bugs and concierge requests go to InspectSync, not to your company's support desk.
- Attachments are welcome on every form. A screenshot or a spreadsheet is usually faster than a paragraph.
- Concierge requests keep a status. They are the one form here that comes back as a grid you can check on.
- Three request types. API Catalog Request, File Catalog Update and Configuration Assistance cover what the concierge service does.