How Email Verification and Integration Setup Works

Source: autosoft-workshop/app/controllers/sessions_controller.rb, companies_controller.rb, application_controller.rb

• If email verification status is "Pending", the system triggers an AWS SES verification check on every login until resolved
• Domain verification is only checked if the verification email was sent within the last 72 hours — after that, the check stops and status stays pending
• Vehicle Visuals credentials are verified and cleaned (whitespace trimmed, validated) on every login
• Gold or Platinum subscription automatically triggers public booking diary token setup on login — no manual configuration needed
• A HubSpot emergency shutdown flag exists that skips all HubSpot API calls — used when HubSpot is down to prevent login delays
• Database errors of the PG (PostgreSQL) type are intentionally NOT written to the ErrorLog table — they only appear in server logs
• Canadian companies are automatically assigned a special SMS virtual number for sending text messages
• Vendor integrations (Repco, Fulcrum, Burson, etc.) require a valid vendor record to exist before the integration can be activated

Support scenarios

• "Email verification has been pending for days" → the 72-hour check window expired; verification email needs to be re-sent to restart the check cycle
• "Login is slow" → could be SES verification check running on every login, or HubSpot calls if the shutdown flag isn't set during an outage
• "Public booking diary set itself up" → Gold/Platinum subscription auto-creates the booking token on login
• "Can't find the error in ErrorLog" → PostgreSQL-type errors are excluded from ErrorLog; check the server logs instead
• "SMS isn't working for our Canadian customer" → verify that the special Canadian virtual number was assigned correctly
• "Can't connect Repco/Fulcrum integration" → a valid vendor record must exist first before the integration can be set up