Service catalog
Present request types with description, audience, deadline, and required data.
OmniSmart Solution · Request portal
Request portal for every request start off on the right foot
Provide an organized entry point for customers, partners, or teams. The requester chooses the service, submits the necessary data, and tracks the status; the operation receives context to execute.
Request catalogForms per serviceStatus and communication
appsRequest portal
AVAILABLE CATALOG
Service12 optionsorganized catalog
EntryFormconditional fields
TrackingBy protocolvisible status
A single entry point for each service
appsCatalogChoose service
dynamic_formRequestSubmit context
confirmation_numberProtocolDeadline provided
track_changesTrackStatus and pending items
infoThe portal organizes the entry and starts the appropriate workflowVISUAL EXAMPLE
One entry pointEntry organized by service
Right dataFields and documents by category
RoutingTeam, priority, and SLA
TransparencyStatus and updates for the requester
Direct answer
What is a request portal?
A request portal is an interface where customers, partners, or employees choose a service, submit data and documents, and track progress. Each submission starts a process with defined category, assignee, priority, deadline, and communication.
- The catalog guides what can be requested.
- The form changes according to the service.
- Status reduces duplicate inquiries.
- The request feeds a trackable process.
Structured entry
A good process starts before the first task
When a request arrives as a free-form message, the team has to figure out category, urgency, customer, and missing data. The portal anticipates this organization and starts the flow with sufficient context.
Conditional forms
Show fields and documents based on the requester's choices.
Profile-based access
Organize what customers, partners, or teams can view and request.
Automatic routing
Direct category, team, priority, and flow based on the information received.
Status tracking
Allow checking progress, pending items, and completion without asking for updates through another channel.
Process communication
Send confirmations, requests for additional information, and change notifications based on events.
From catalog to completion
The request comes in ready to be worked on
The portal connects the requester's experience to the executor's routine.
Choose the service
The requester finds the category and understands what will be needed.
Submit the data
The form collects context, documents, and required information.
Receive protocol and deadline
The entry is recorded and the initial expectation is clear.
Track and supplement
Status and pending items appear during execution.
Complete and learn
Outcome, time, and feedback feed service improvement.
Impact on operations
What changes in practice
Processes become faster when input, rule, responsibility, and exception use the same reference.
Comparable requests
Common categories and fields facilitate distribution and volume analysis.
Less back-and-forth
Required data reduces the initial search for missing information.
Transparent status
Requesters can track progress without generating parallel inquiries.
Demand-driven catalog
Volume, deadlines, and feedback help improve services and forms.
Who it makes sense for
Processes for operations that need scale and control
B2B customer serviceCustomer SuccessImplementationInternal supportPartners and suppliersShared services
Frequently asked questions
Learn more
The portal is the entry and tracking interface. The help desk is a ticket and support operation. They can work together when a request generates a ticket.
Yes. Fields, options, attachments, and instructions can vary by category and previous answers.
They can track steps and updates defined for the audience, respecting permissions and internal information.
Yes, as long as the catalog, access, data, and communication are designed for each audience.
Yes. Each submission can start routing, tasks, approvals, SLA, documents, or integration according to the process.
Start with frequent requests, name them in the requester's language, and include the objective, required data, deadline, and exception channel.
Talk to OmniSmart
Organize the entry point for your requests
Share audiences, request types, data, and responsible parties. OmniSmart helps design the catalog, forms, and tracking flow.
Chat with a specialist
Tell us the basics about your scenario.