Skip to main content

​
Overview

Rex is a CRM integration. Connecting it links your Rex account to your Voxworks team for two things:
  • Booking: the Book Calendar Appointment | Pro tool can check calendar availability, create appointments against your Rex calendars, and attach those appointments to Rex contact records during a call.
  • Importing: Voxworks can import your Rex listings, account users and contacts as custom variables, and turn the contacts into contact records your batches can call. See Importing from Rex.
The Rex card in the app carries a CRM badge and the description “Fetch live CRM data at call start and sync call results back to Rex”. Unlike most integrations, Rex does not use an API key or an OAuth redirect. It uses a session login: you enter your Rex email and password once, Voxworks verifies them live against Rex, then encrypts and stores them and keeps the connection alive automatically from that point on. Until Rex (or another calendar provider) is connected, the calendar booking tool does not appear in the script editor’s tool picker at all — connecting is the prerequisite before any Rex booking can be configured.
Integrations are typically built out for specific clients, so the full functionality of Rex’s interface might not be available. If your team needs additional features from this integration, contact the Voxworks team directly to discuss what can be added.

​
Connecting Rex to Voxworks

  1. In the sidebar under Admin, open Integrations.
  2. In the Available Integrations section, find the Rex card and click Connect.
  3. The Connect Rex dialog opens: “Enter your Rex login credentials. We’ll verify them and securely store them.”
  4. Fill in both fields and click Connect.
The Connect button stays disabled until both fields are filled in. A note in the dialog confirms how the credentials are handled: “Your credentials are verified on connect, then encrypted and stored. We re-authenticate automatically when the session token expires.” When you click Connect, Voxworks performs a real sign-in to Rex with the details you entered. If Rex rejects them, the connection is not saved and an error is shown — correct the email or password and try again. On success, the Rex card moves to the Connected Integrations section with a green Connected badge, and the card’s footer shows how many tools the connection makes available.
Use a Rex account that can see the calendars you want the assistant to book into. Appointments created on calls are made by this account, so a shared or dedicated Rex user keeps them easy to identify.

​
How the connection stays authenticated

Rex issues short-lived session tokens rather than permanent keys. Voxworks handles this for you:
  • At connect time, your credentials are exchanged for a session token. The credentials and the token are both encrypted before they are stored — neither is ever displayed again.
  • When the token nears expiry, Voxworks signs in to Rex again with your stored credentials and mints a fresh token automatically. This happens behind the scenes; there is nothing to renew, rotate, or re-enter.
Automatic re-authentication uses your stored Rex password. After you change your Rex password, click Reconnect on the Rex card (or open the Rex page, Disconnect, then Connect again) and enter the updated login so availability checks and bookings on calls keep working.

​
What connecting unlocks

Once Rex shows as Connected:
  • Book Calendar Appointment | Pro appears in the tool picker when you edit a script step. The picker hides integration-bound tools until their provider is connected.
  • With Rex as the provider, the tool adds Rex-specific fields alongside its shared settings — most notably a required contact_id (string, e.g. 998877) identifying the Rex contact the appointment is attached to, and a required title (string, e.g. Property appraisal). Both accept a literal value or a variable — type / in the field to insert one. Optional fields cover the calendar, staff, duration, location, and business hours; the full field-by-field reference lives on the Rex booking tool page.
  • If your team has more than one calendar provider connected, a provider select appears in the tool’s configuration panel so you can choose Rex explicitly.
Successful bookings are written to {{calendar.*}} variables your flow can speak or send — for example {{calendar.booking_time_spoken}} (string, e.g. 10:30 AM on Tuesday the 22nd of July) and {{calendar.booking_id}} (string, e.g. bkg_01HZXW). The settings shared by every calendar provider (availability window, SMS confirmation, timezone check) are on the calendar tools overview.

​
Team-level calendar defaults

Two Rex-specific fields can be left blank on a script step and fall back to a default configured against your team’s Rex connection, so every script on the team can book into the same calendar with the same staff without repeating the setup: contact_id and title are always required on the script step itself — each booking needs its own contact and appointment title, so neither has a team-wide default. If duration_minutes is left blank, the appointment defaults to 30 minutes. These team-level defaults have no configuration screen in the app. Speak to the Voxworks team to set or change them.

​
Importing from Rex

Click the gear icon on the connected Rex card. It opens a full page for the connection (the same layout as Agentbox). The header shows Status, Connected (how long ago), Auth (Rex login) and Data (Read only): importing reads from Rex and nothing is written back.

​
What to import

“Narrow the records pulled from Rex. Leave the filters empty to import everything.” There is no match preview for Rex.

​
Fields to import

“Everything Rex sends and where it will land. Untick anything you would rather not store — identifiers and sync state are needed to match records, so they stay on.” Fields are grouped by record type; use Expand all / Collapse all to see them all.

​
Initial import

“Pulls everything matching the filters above. It runs in chunks, so you can pause and pick it up later.” Click Start import. Records are imported in phases (Properties, Agents, Contacts) with progress shown as Importing or Paused at, Imported so far and Completed. Pause stops the import; Resume carries on and Restart begins again. Once finished, Run import again re-imports with the current filters, which is how you pick up changes made in Rex. Each property, listing and account user is read in full (listing status, dates, prices, inspections, media, tenancy details and attributes). A value missing from Rex never clears data Voxworks already holds. If some records could not be read in full, the page warns: “N record(s) could not be read in full, so only summary fields were stored. Addresses, features and role flags will be missing on those.” Run the import again to retry them.

​
Sync to contacts

“Turns the imported contact profiles into contact records the dialler can use. Runs against what is already imported, so it makes no Rex calls.” The results show Contacts created, Contacts updated, Skipped (no phone number, or a duplicate of one already imported) and Could not be built. Each contact profile is linked to its contact record. Contacts are matched on their phone number in any format, so a Rex contact stored as 0412 345 678 updates an existing Voxworks contact with +61412345678 rather than creating a duplicate.

​
Disconnect

The last section of the page: “Disconnecting stops all active workflows using Rex tools. Imported records stay in place.” Click Disconnect to remove the connection; there is no confirmation step. Any script step still configured with the Rex booking tool will fail to book until you reconnect, and records already imported are kept. You can reconnect at any time by entering your Rex login again. If the connection fails (for example after a Rex password change), an Error badge appears on the card with the error message, the card offers a Reconnect button that reopens the connect dialog, and the error is shown on the Rex page.

​
Next Steps