Skip to content

Deciding when to ask people to sign in · 3 min read

Do your customers need an account to use your website?

Before requiring customers to sign in, work out what they came to do and what information they need to reach later.

Start here.

Let people complete simple tasks without creating an account when you can do so safely. Verify access before showing private records. Offer an account when customers need ongoing access to several tasks, records or shared responsibilities.

  • Ask what an account enables at the point where you require it.
  • Give customers a clear way to continue without an account where appropriate.
  • Test recovery and access to private records before launch.

Start with what the customer came to do

Imagine a neighbourhood camera repair shop. A first-time customer wants to ask whether the shop can fix a lens. A returning customer wants to see notes on an open repair. A business that sends equipment every week wants its team to see several repairs in one place.

Those people need different things. Before asking everyone to create an account, decide what each person needs to do today, whether they need to come back, and what you have to verify before showing private information.

Let people finish a simple first task

If the customer only needs to request an estimate, ask for enough information to respond and a way to reach them. Your team can keep a record of the enquiry without asking the customer to choose a password. If both guest and account routes are available, put a clear “Continue without an account” option where people will see it.

Baymard’s checkout research documents people missing guest options when the sign-in choices are more prominent. Apply the lesson by watching people try your own first task on a phone. Ask them to tell you whether you require an account and what they would tap next.

Protect the next visit separately

For one open repair, the shop might give the customer a way to verify their access to that job alone. Ask the supplier what happens if the message is forwarded, the link expires, or a customer uses a different email. Agree what staff need to check before sending a replacement. Test with sample records so no private information is exposed during the demonstration.

If the customer returns often and needs several jobs, an account can give them a useful place to come back to. Tell them what they get by signing in and decide whether they can create the account after the first task. For business customers, decide who can see which jobs and what happens when someone leaves their team.

Test the difficult visits before deciding

Give these tasks to people who have not seen the design. Ask them to try both the first visit and a return visit. Watch where they stop, what they expect from an account, and whether they know how to get help when they cannot get back in.

Three customer paths for the hypothetical camera repair shop
Customer taskPossible routeWhat to test
Ask if a lens can be repairedSend an enquiry without creating an account.Can a new customer find that route and see what happens after sending?
Check one open repairVerify access to that repair.Can staff help when a confirmation is lost without revealing another record?
Manage repairs for a businessUse an account with access to the right jobs.Can the business remove one colleague without affecting the rest of the team?

Choose the simplest route that protects the work

Ask what a required account makes possible at the exact point where you ask for it. If it only helps staff keep a tidy contact list, look at how your staff tools match repeat enquiries. If it lets a customer safely reach a history they regularly need, show that benefit when you invite them to sign in.

Before paying for an account feature, ask the supplier to demonstrate a lost confirmation and a customer trying to open someone else’s repair. Have your staff show what they would do if the customer can no longer use the original email. Make those outcomes part of what you agree to test.

Use three questions in your supplier demo

Bring a new enquiry, an open job and a repeat customer as sample cases.

What can people finish today?
Which first tasks can customers do without an account?
What can they see later?
How does the service check that someone can open a private record?
Who can help when access fails?
Show what a customer and a staff member see when the original message or account is unavailable.

Planning something with a similar workflow?

Discuss your project with us

A couple of common questions.

Can we still keep a customer record without a login?

Yes. Your team can keep an enquiry or order record independently of whether the customer signs in. Agree how staff identify returning customers without exposing someone else’s history.

Should we offer an account after the first task?

Try offering one with a clear benefit, such as seeing several open jobs. Check whether the customer knows their original request is already complete and whether creating an account is optional.

What should happen when a customer loses a confirmation?

Give them a clear way to get help. Rehearse how staff verify the request before issuing access to a private record, using sample data.

Have something in mind?

Tell us what you want to build or improve. We’ll work out a useful first step together.

Discuss a project