Skip to content
Billisecond

Billisecond support

Tell us what happened, not just that it broke.

Include the product, version, what you were trying to do and what happened instead. A clear description gets us to the useful part sooner.

Useful first checks

Start with the likely causes.

Connection

Billisecond cannot connect

Check that the workstation is on the expected network or VPN and that the organisation’s SQL Server is available. Timers may offer controlled offline recovery while it retries.

Update

An update has not completed

Restart the application once, confirm the workstation can reach the configured update source, then ask an administrator to verify the installed version and release details.

Access

A feature is unavailable

Ask the organisation’s Billisecond administrator to confirm that your security group includes the required application permission.

Safety

A record looks out of date

Refresh before repeating the change. Billisecond uses version checks to stop an older edit from silently replacing a newer shared record.

Contact Billisecond

Send a message to the team.

Choose the reason for your enquiry and provide the information needed to respond. We will reply to the address you provide.

Do not include passwords, licence keys, SQL credentials, pairing codes or client-sensitive records.

Deployment enquiries

Planning a rollout or adding another application?

Include the number of Windows workstations, the applications required and whether your organisation already operates SQL Server.

Discuss your rollout