Settings & credentials
Connect the services that power sending and calling.
Settings is where you connect the external services ReachConvert orchestrates. Credentials are stored encrypted, and each integration has a test button so you can verify a connection before you rely on it.
Before you begin
- Provider credentials from AWS, Twilio, or Google, depending on the channels you plan to use.
End-to-end operator flow
- 1Start: open this feature from the dashboard sidebar and confirm your prerequisites are connected in Settings.
- 2Configure: complete the required fields and selections for your target audience and objective.
- 3Launch: run the action immediately or schedule it for later based on your workflow.
- 4Monitor: watch status, history, and dashboard metrics to confirm progress and outcomes.
- 5Troubleshoot: if results stall, verify credentials, audience data quality, and feature-specific validation messages.
Integrations
AWS SES
Powers email delivery. Add your access key, secret, region, and sender address, then Test SES.
Gemini (Live)
Powers VoiceReach and signal classification. Add and verify your Gemini API key.
Twilio
Places the actual phone calls. Add your account SID, auth token, and phone number.
Gemini (Text)
The same Gemini key backs AI text generation for templates. Pick a cheap text model such as gemini-2.5-flash-lite.
Keep provider credentials private
Enter credentials only in Settings. Do not place access keys in templates, contact fields, screenshots, or frontend environment variables that are exposed to the browser.
Verifying connections
- 1Enter credentials for a service.
- 2Click its Test button — a live check confirms the keys work.
- 3A connected status unlocks the related feature (e.g. Gemini “Connected” enables VoiceReach).
Tips
- Use the SES sandbox (verified recipients only) to test campaigns without reaching real prospects.
- Stored credentials are encrypted at rest and masked in the UI once saved.