Configure Customer Sign-In

Open Settings in the Admin Panel, then select Customer Sign-In. This setting controls how customers confirm registration and later sign in to the customer app for this company.

Use email codes

Select Email code. Frequenta saves the channel immediately and sends customer verification codes by email. No provider configuration is required.

Use email when you do not have Twilio credentials or do not want the business to pay for SMS delivery.

Configure SMS codes

Before selecting SMS, obtain these values from the company’s Twilio account:

• Sender number — the Twilio number that sends the message; some supported countries allow an alphanumeric sender ID;
• Account SID;
• Auth Token.

Enter all three values, then select SMS code. Frequenta saves the credentials and changes the customer channel together. A success message confirms the saved result.

Frequenta creates and verifies each code. Twilio only delivers the message, so this form does not require a Twilio Verify service.

What the channel change does to customers who already joined

The two channels recognize an account differently. A customer who joined by email is known by the address they gave. A customer who joined by phone is known by their number alone: the program never asked them for an address and does not have one.

That makes the change different in each direction.

Email to SMS carries customers across. Everyone who joined by email keeps their account, their visits and their rewards, and signs in with the phone number already on their record. The SMS code choice states how many customers this applies to, and the confirmation after saving repeats the number.

SMS to email is refused while the program has customers who sign in by phone. They have no address to receive a code at, so the change would leave them outside a program they are already in. The Email code choice says how many customers that is and stays unavailable until there are none. Switching is possible again once no customer signs in by phone.

Plan the channel before the program opens to customers. It is the one setting whose cost grows with every person who joins.

Replace saved credentials

When the status says Twilio credentials — saved, the secret fields remain empty. Frequenta does not return the saved Account SID or Auth Token to the browser.

To rotate a value while SMS is selected:

1. Enter each replacement value. Leave a field empty only when its current value should remain unchanged.
2. Select Save credentials.
3. Wait for Customer sign-in settings saved before closing the page.

Never place an Auth Token in a screenshot, support message, or shared document.

Recover from an error

• If the page says the settings could not be loaded, refresh the company Admin Panel before changing the channel.

• If Frequenta asks for the Account SID, Auth Token, and sender, complete all required SMS values and select SMS code again.

• If saving fails, the previous channel and credentials remain authoritative. Do not assume that SMS is active until the success message appears.

• If Frequenta says that customers sign in by phone and would lose access, the channel is unchanged and SMS remains active. This is not a save failure: it is the cost of the change, stated before it happens.

When SMS delivery is unavailable, switching back to Email code is possible only while no customer signs in by phone. Provider billing, sender eligibility, and country restrictions are managed in the company’s Twilio account, not in Frequenta.