How Relay Assist Integration Works

Source: relay_assist_controller.rb

• Required fields for enrolment: customer must have name, state, email, mobile, and postcode; vehicle must have plate number, make, model, build date, and body type
• The system prefers the mobile number over the phone number; if both exist, mobile takes priority
• If the customer does not have a relay_service_id, the system auto-creates a new customer in Relay Assist rather than failing
• At least one available sticker or membership must exist in inventory before enrolment can proceed
• Service interval is hard-capped at 6 months; membership expiry is set to 6 months plus 1 day from enrolment
• Sync operations process customers in batches of 10; matching between systems is done by plate number only

Support scenarios

• "Relay Assist enrolment is failing with missing fields" → Check all required fields: customer needs name, state, email, mobile, and postcode; vehicle needs plate, make, model, build date, and body type. All must be populated.
• "Customer was duplicated in Relay Assist" → If the customer record in Workshop does not have a relay_service_id, the system creates a new Relay Assist customer instead of matching the existing one. Check for the relay_service_id field.
• "Relay Assist sync missed some customers" → Sync matches by plate number only. If a customer's vehicle plate changed or is missing, the sync cannot match them. Also, sync processes in batches of 10, so large datasets may take multiple cycles.
• "Membership expired sooner than expected" → Membership expiry is automatically set to 6 months plus 1 day from enrolment. This is hard-coded and cannot be adjusted per customer.