A clear starting point for setup, updates and product questions.
Bring the exact product, supported environment and task into one conversation. Whether your UK business is preparing an installation or investigating an issue, the shared documentation and Bazecity account help keep the instructions, licence and support history connected.
Use the current product information to check the fit. If a requirement is essential and not documented, ask about it before ordering.
Compatibility questions
Include your platform and runtime versions and any related software the product must work with.
Feature questions
Describe the task you need to complete rather than asking only whether the product can do everything.
During installation or setup
Follow the guide for the product and version you have. If the result differs, note the exact step and what happened before changing unrelated settings.
Setup context
Include the product version, hosting or platform requirements and the instruction you were following.
Useful evidence
Send exact errors and relevant screenshots with private information removed.
Access requests
Ask the support team how to provide any needed access. Keep passwords and recovery codes out of general messages.
After the product is in use
Describe the affected task, the users involved and any recent changes. Use the existing request for the same issue so earlier checks remain available.
A repeatable issue
List the actions that reproduce it and say whether it happens consistently.
A new requirement
Explain the desired behavior separately from a fault. Custom changes may need an agreed development scope.
Open and manage Bazecity support tickets at app.bazecity.com/support. Sign in to your Bazecity account to follow the conversation and keep your requests together.
Give the person helping you the details that matter.
Prepare a useful installation brief
Identify the website or application, its platform version and any existing configuration the product must work alongside. State whether this is a fresh installation, an upgrade or a move between environments. Confirm access, backups and the planned review steps before changes begin. Keep passwords and private keys out of public messages and share access only through an agreed method.
Separate product guidance from additional project work
Explain what you expected to happen, what occurred and the steps needed to reproduce the issue. Product documentation can answer standard configuration questions, while custom changes or third-party troubleshooting may need a separate scope. Check the applicable support and licence terms in your account, and agree who will test the outcome and maintain the setup afterwards.