Customer view
- Request
- REQ-1042
- Customer
- Sample customer A
- Work requested
- Reception display installation
- Request status
- Needs information
- Site access plan
- Missing
Please share the site access plan with your project contact.
Customer portals
Give customers a place to send requests, share documents and follow progress, with a clear handoff to your team.
Start a projectFollow the request
A customer asks for work. Someone on your team reviews the request, asks for a missing detail and passes an approved brief to the person doing the job. A portal gives both sides a record to return to, with different views of the same request.
Snoogz connects customer and client portals to the tools your team uses. You work directly with Jacky Pham, based in Port Coquitlam and working remotely, on an agreed project through implementation and handover. We define what customers can do, how staff respond and where the records belong.
Two sides of a request
The example below follows an installation request. The customer needs to supply a site access plan. Staff need to check that plan before preparing the installation brief. Each view shows the information needed for that part of the work.
From request to handoff
A fictional request shown in three prepared stages. The tabs switch views without submitting or saving information.
Staff view
- Request
- REQ-1042
- Customer
- Sample customer A
- Work requested
- Reception display installation
- Request status
- Needs information
- Site access plan
- Missing
- Owner
- Alex (sample)
The request is waiting for the site access plan.
Internal note
Confirm building access before preparing installation brief.
Customer view
- Request
- REQ-1042
- Customer
- Sample customer A
- Work requested
- Reception display installation
- Request status
- In review
- Site access plan
- Received; access details under review
The site access plan has been received. Your request is being reviewed.
Staff view
- Request
- REQ-1042
- Customer
- Sample customer A
- Work requested
- Reception display installation
- Request status
- In review
- Site access plan
- Received; access details under review
- Owner
- Alex (sample)
Review building access and prepare the installation brief for approval.
Internal note
Check the access details against the brief before approving the handoff.
Customer view
- Request
- REQ-1042
- Customer
- Sample customer A
- Work requested
- Reception display installation
- Request status
- Complete
- Site access plan
- Reviewed; building access confirmed
Approved installation brief handed to scheduling.
Staff view
- Request
- REQ-1042
- Customer
- Sample customer A
- Work requested
- Reception display installation
- Request status
- Complete
- Site access plan
- Reviewed; building access confirmed
- Owner
- Alex (sample)
Approved installation brief handed to scheduling.
Internal note
The request handoff is complete. Installation has not been marked complete.
The approved brief is now with scheduling. Installation follows as a separate job.
A live portal also needs sign-in and tested permissions for each customer and staff role.
Choose access deliberately
The scope should identify who can see each request, who can change it and which notes remain internal. It should also cover invitations, departing staff, account recovery and customers who share an organization account.
Files need decisions of their own: allowed types and sizes, where they are stored, who can download them and when they should be removed. Notification messages should reveal only the information needed to prompt the next action.
Configure or build
Your CRM, helpdesk or membership platform may already include a suitable portal. We check its existing features, configuration and connectors before proposing a separate product. Its permissions, file handling, exports and ongoing charges need to fit the work you do.
A custom portal becomes worth considering when the shared products leave important steps outside the system, or when staff need to act on records held elsewhere. We check the available connections and decide which system owns each record. See workflow automation for how matching and updates should be planned.
A first version
For the illustrated workflow, a first release could cover customer sign-in, one request type, a file requirement, a staff review queue and a customer-visible outcome. The scope would define the permitted status changes and the message shown when information is missing.
Payments, live chat, appointment booking and multiple service types would be separate decisions. Keeping those boundaries explicit lets us review a complete request journey before adding more ways through it. The cost and scope guide shows how those choices affect the work.
Records and running costs
If requests already exist in email, a spreadsheet or another tool, we decide what needs to move and how to check it. An initial release may start with new requests while older records remain available elsewhere. A full migration requires its own mapping and reconciliation.
Before launch, we discuss hosting, account and source access, storage charges, backups, exports and who handles customer access problems. Maintenance and support responsibilities belong in the agreement, including what happens when an external service changes.
Before we start
Can it use our current systems?
Possibly. We need to check whether those systems expose the required records and actions, and under which access and subscription terms. A sample request and a list of your current tools help define that assessment.
How do we decide the first scope?
Start with one request and the people and systems involved. If important access or workflow questions remain, a standalone assessment can establish the options before implementation is quoted. See the assessment options and starting prices.
Can we start without payments?
Yes. A request and document workflow can be a complete first project. Payments or billing connections can be considered separately when the work calls for them.
Who manages customer accounts?
That needs to be assigned before launch. The project should define who invites customers, changes access, handles account recovery and removes accounts, along with the software and instructions they need.
Start a project
Tell me which workflow or system needs attention. Five short questions help outline a review, project or embedded engagement you can discuss by email.
Start a project Review your brief, then continue in email.Prefer email?jacky@snoogz.ca
Snoogz Software is based in Canada and uses Google Workspace for email. These services may process your information outside your country. Please avoid sensitive personal information. Read our privacy notice.