01
The affected task
Explain what the user is trying to do, which system is involved and whether the issue affects one person or a wider team.
Technical assistance
Start with the task your team cannot complete.
Describe the affected system, the people involved and the result you expected. We can review the issue and the appropriate support or project route with the operating context of your Nigerian business in view.
Make the issue easier to understand
02
Evidence and recent changes
Include the exact error, relevant timing and steps that reproduce the issue. Mention recent updates or configuration changes and remove private data from screenshots.
03
Access and authorization
Confirm who owns the system and can approve changes. Use an agreed secure process for any access needed; keep passwords and recovery codes out of ordinary messages.
Separate troubleshooting from planned improvements
01
Existing product support
For a Bazecity product or service already in use, open the appropriate support request with the product version and purchase or service reference.
02
Maintenance requirements
Describe the systems and recurring checks you want covered. Availability, response arrangements and ongoing responsibilities depend on the agreed service.
03
A change to the system
New features, migrations and additional integrations may require a separate project scope. Describe the desired behavior clearly so it can be assessed.
Keep one history for the same issue.
Use the existing support conversation for follow-up and provide the result of earlier checks. For a new environment or ongoing support requirement, request a scoped discussion.
BAZECITY NIGERIA
Plan around the way your team works.
Separate an incident from a planned improvement
For an incident, share the timing, exact error, affected users and recent changes. For ongoing maintenance, list the systems and recurring checks you want covered. Explain whether the requirement can be handled remotely or may need on-site work; location, availability and delivery arrangements need an agreed scope.
Keep changes authorised
Identify the system owner and the person who can approve access or configuration changes. Keep passwords and recovery codes out of ordinary messages. Support availability, response arrangements and any recurring maintenance responsibility depend on the service or written agreement you choose.