Onboarding Prep & FAQ

Before you start

Audienti setup is usually straightforward if the right details are ready before the session. The goal is to get connected cleanly, keep control tight, and start with a conservative operating posture.

Have these ready

The login email, username, or profile name you use for each account you plan to connect.
The current password for each account.
Your two-factor authentication device or method so you can approve login requests.
Your phone number, ZIP code, and country, since some networks may ask you to confirm those details during login.
Your two-factor authentication secret, if you already have it saved somewhere.

Recommended accounts to connect

If possible, connect both your email account and your LinkedIn account. Connecting both gives Audienti a better working surface and usually makes the system useful faster.

Gmail setup

If you are connecting Gmail, we will send you a link to create a Google App Password.

This is a separate password just for the application.
It can be revoked from your Google account at any time.
It is often the cleanest way to let the system log in on your behalf while keeping that access easy to remove later.

Optional 2FA shortcut

If you can provide your two-factor authentication secret, there is a place to enter it during setup. That can reduce repeated authentication prompts later. If you do not have it, you can still complete setup normally.

What to expect during onboarding

During setup, you may be asked to:

Enter your password.
Approve a two-factor authentication request.
Confirm details like your phone number, ZIP code, or country.

That is normal.

Final check

Before the setup session, please make sure you can access:

The account login you use.
The current password.
The device that receives authentication codes.
Any backup verification details tied to the account.

If you have those ready, setup is usually quick.

FAQ

Does connecting my inbox give other teammates full access to my private email?

No. By default, private conversations stay private.

Audienti can support a unified inbox, but that does not mean your full private inbox becomes visible to everyone else. What flows into broader account context are prospect conversations tied to pre-identified prospects inside the system. If someone is not already a prospect in that account context, their private thread does not automatically become shared team context.

If you want a person to become visible in a project or account, you can explicitly promote them into that project or account as a prospect. That is a deliberate action, not the default.

Can I remove a social account later?

Yes. You can remove a connected social account at any time.

Historical conversations and prior activity remain in the system as record history, but once the account is removed, no new sync or live connection continues from that account.

After I connect an account, can every project or subaccount use it automatically?

No. After an account is connected, you still choose which project or subaccount is allowed to use it.

The main project may be the default starting point, but every additional project or subaccount must be explicitly allowed. This keeps access controlled and prevents a connection from being used everywhere automatically.

Do I need to turn on autopilot right away?

No. Autopilot can be fully turned off.

Even with autopilot off, the operator panel still shows follows, activity, and the working queue so you can review what is happening and stay manual while the system gets dialed in.

The practical recommendation is to start conservatively on connection requests and ramp over time. A reasonable pattern is roughly:

Week 1: 5 per day.
Week 2: 10 per day.
Week 3: 20 per day.
Week 4: around 25 per day if everything looks healthy.

The point is not to force volume early. The point is to establish stable behavior first, then increase throughput gradually.

Is there a deeper autopilot mode once the system is working well?

Yes. There is a fuller autopilot mode for later.

Once the system is dialed in and you are comfortable with the behavior, you can choose which activity types the agent is allowed to take automatically. That gives you a more advanced autopilot configuration without forcing you into it on day one.

Agent contract

Use: prepare a user for onboarding and account connection before a setup session.
Inputs: login identity, passwords, app passwords, two-factor method, phone/ZIP/country checks, accounts to connect, and automation comfort level.
Surfaces: Onboarding Prep, Social Accounts, Workspace Setup, Autopilot, and Account Maintenance.
Verify: confirm the user can access every account, receive authentication prompts, and understands conservative launch expectations.
Never: ask for credentials in shared prompts or imply connected inboxes automatically expose all private email to teammates.