Step-by-step guide to install Your Booking for your practice.
Your Booking is an online appointment booking system for optometry practices using Optomate Touch. A lightweight agent runs on your practice server and connects securely to the Your Booking platform. No patient data is stored outside your practice.
Before installing the agent, configure Optomate Touch for API access.
YOURBOOKING — this appears as the staff code on appointments created by the booking system| Resource | Read | Create | Update | Notes |
|---|---|---|---|---|
| Appointments | Yes | Yes | Yes | |
| Branches | Yes | |||
| Business Details | Yes | |||
| Online Appointment Types | Yes | |||
| Optometrists | Yes | |||
| Patients | Yes | Yes | Yes | |
| Sources | Yes |
If you plan to use the Recalls & Reminders module (can be enabled later), also add:
| Resource | Read | Create | Update | Notes |
|---|---|---|---|---|
| Patient Recalls | Yes | Yes | Read to fetch due recalls; Update to mark as sent | |
| Recall Types | Yes | Recall type sync for template mappings | ||
| Patient Notes | Yes | Yes | Stamp recall and feedback replies on the patient record |
Open a browser on the server and navigate to:
http://localhost:12000/OptomateTouch/OData4/Branches
Because the browser doesn't send any login details, you'll get a short "missing credentials" error, like this:
{"error":{"code":"100","message":"Missing Credentials!"}}
This is expected and is exactly the result you want — it confirms the API is running and reachable. You do not need to see your branch details at this step.
If instead the page won't load at all — "can't connect", "connection refused", or it times out — then the API isn't reachable: check that Optomate Touch is running and the API module is installed.
If the page loads but shows a long error message mentioning BranchesController or "the underlying provider failed on Open", the API is installed and running correctly but can't reach the Optomate database. There are two possible causes.
First, the quick one. In Services, find the entry starting with SQL Server and make sure it is Running, with Startup Type set to Automatic. A recent restart can leave it stopped. If that wasn't it, read on.
Second, a known bug in the Optomate API installer. This one is not something you've done wrong. The installer writes a configuration file that leaves out the name of the database instance, so the API has no way to find your Optomate data. It's a one-line correction, and you have three ways to get it done:
Data Source= line described below and we'll tell you exactly what it should say, or we can walk through it with you on a screen-share.C:\Optomate Touch\Optomate API Host Service. Find the Optomate API program file (the application), then look for the file with exactly the same name plus .config on the end — that's the one you want. On the small number of servers where the API runs under IIS, the file is C:\Optomate Touch\Optomate Touch API\web.config instead. Open it in Notepad — run Notepad as Administrator first (right-click → Run as administrator), or it won't let you save.SQL Server (SQLEXPRESS).<connectionStrings> section and look for Data Source=. It should read localhost\ followed by the instance name from the previous step — most often localhost\SQLEXPRESS. Two versions of this are commonly wrong:
localhost, with no instance name — add the one you found.DESKTOP-12AB34C\SQLEXPRESS — replace the computer name with localhost, keeping the part after the backslash.iisreset from an Administrator Command Prompt.)A note on the Your Booking status showing Offline: the agent won't connect to us until it can talk to Optomate, so an Offline status alongside a healthy-looking agent service almost always points at Optomate rather than at the agent.
Once the check above succeeds, restart the agent: open Services, find YourBookingAgent, and choose Restart. The status should turn green within a minute. You don't need to reinstall anything.
Download the installer from:
https://yourbooking.au/downloads/YourBookingAgent-Setup.exe
Run it on the practice server.
The default location is C:\Program Files\YourBookingAgent. You can change this if needed.
The installer will prompt for:
| Setting | Description |
|---|---|
| Licence Key | Your practice licence key (provided during onboarding) |
| Optomate Server | Usually just localhost — change only if Optomate is on a different machine. Accepts hostname, host:port, or a full URL. |
| Optomate Username | The API username created in Step 1.1 |
| Optomate Password | The API password created in Step 1.1 |
The installer will:
YourBookingAgent) that starts automatically on bootOpen your practice's booking page (e.g. yourpractice.yourbooking.au) in a browser.
Once the agent is installed and connected, follow the Setup Guide to configure the booking system. This covers:
Online booking is off by default, so you can take your time configuring everything before patients can see the booking page.
By default, patient emails (booking confirmations, reminders, recalls, follow-ups) come from bookings@yourbooking.au with your reception address as the reply-to. To have them come from your own address instead — either by adding DNS records to your domain, which needs no password, or by sending through your own Gmail or Outlook account — see the Practice Branded Email guide.
To embed the booking page on your website, see the Website Integration Guide. It covers the iframe embed code, configuring email links, and optional redirect rules for SMS/recall links.
Set up a tablet in the waiting room so patients can book themselves when staff are busy.
https://yourpractice.yourbooking.au/?kiosk in Safari on the iPadThe app launches full-screen with no browser chrome. It shows a welcome screen with the practice logo and a "Book an Appointment" button. After a booking completes or 2 minutes of inactivity, it resets back to the welcome screen for the next patient.
iPad setup for shared use:
Disable autofill so patients don't see each other's saved information:
Patients can add the booking page to their own phone's home screen by visiting https://yourpractice.yourbooking.au/ directly and choosing "Add to Home Screen". This gives them a branded app icon and a full-screen booking experience. If you've uploaded a square icon in Branding → Square icon, that's used for the home-screen icon — otherwise your main logo is used (which may look cropped on square icon slots).
Patients who visit the booking page via your own website (the embedded iframe) need the additional manifest setup described in the Website Integration Guide → Step 4: Add to Home Screen to get the same experience.
The agent only makes outbound connections. No inbound firewall rules or port forwarding are required.
If your network has outbound filtering, ensure the server can reach:
yourbooking.au on port 443 (HTTPS/WSS)To change the Optomate API credentials or other settings:
.env file in the install directory (e.g. C:\Program Files\YourBookingAgent\.env)services.msc, find "Your Booking Agent", right-click → Restartwinsw restartAgent logs are at logs\winsw.err.log in the install directory. To view:
type "C:\Program Files\YourBookingAgent\logs\winsw.err.log"
Log files rotate automatically at 5MB.
The agent runs as a Windows service called YourBookingAgent. You can manage it from the Windows Services console (services.msc) or from the command line:
winsw start
winsw stop
winsw restart
winsw status
Run these from the install directory (e.g. C:\Program Files\YourBookingAgent).
Use Add or Remove Programs in Windows Settings, or run the uninstaller from the Start Menu. This stops the service, removes it from Windows, and deletes all installed files.
type "C:\Program Files\YourBookingAgent\logs\winsw.err.log".env file has all required valuesservices.msc.env match what you configured in Optomate's API Access settingshttp://localhost:12000/OptomateTouch/OData4/Branches in a browser on the server — a Missing Credentials! error means it's reachable and running; "can't connect" or a timeout means it isn'twinsw status (from install directory) or check Windows Services