How should I use Missions in SalesScreen?

Role: All users, Managers and Company Admins
​Plan: Scale, Pro and Enterprise

On Scale, users can create Missions for themselves. On Pro and Enterprise, managers and admins can also create Missions for users they manage.

Large goals can feel distant and difficult to act on.

Missions help you break them into smaller, time-bound commitments that are easier to understand and complete. Instead of saying, “I need to perform better this quarter,” you can define what progress should look like today, this week or this month.

A Mission can combine:

This means a Mission can connect measurable performance with actions that are not automatically tracked in SalesScreen.

The goal is not simply to complete a checklist. It is to turn intention into action, make progress visible and build habits that lead to stronger results.

If you are an end user: Missions help you take ownership of your next goal. Use them to define what you want to accomplish, track your progress and stay accountable to the commitment you have made.

If you are a team leader or manager: Missions help turn coaching conversations into clear follow-up. Use them to agree on specific actions, reinforce individual priorities and recognize progress between one-to-one meetings.

If you are an admin: Missions help create a repeatable structure for goal-setting across the organization. Use Mission Blueprints to make recommended challenges easy to discover and connect them to current business priorities.

Before creating a Mission, decide what success should look like.

A good Mission could help someone:

Avoid vague goals such as:

Work harder this week.

Use a clear commitment instead:

Book five qualified meetings and follow up with ten priority opportunities by Friday.

A Mission should make the next action easier to understand.

Milestones are the individual commitments that make up a Mission.

Use a combination of milestone types when it helps create a complete plan.

Use a metric when progress should update automatically from connected SalesScreen data.

Examples:

Use an achievement when the Mission should include a meaningful badge or performance milestone.

Examples:

Use a to-do item for an action that is not automatically measured in SalesScreen.

Examples:

Metric progress updates automatically, while to-do items must be checked off manually before the Mission period ends.

Keep the number of milestones focused. Every milestone should support the main outcome of the Mission.

Give the Mission enough time to be meaningful, but not so much time that it loses urgency.

Common periods include:

Short Missions create immediate focus. Longer Missions work better when the outcome requires repeated effort.

Choose a period that matches the behaviour you want to build.

Missions can show difficulty levels such as:

For metric milestones, difficulty is based on the goal compared with historical performance. Achievement difficulty is informed by how often the achievement has been unlocked recently.

Use the difficulty level to make the Mission ambitious without making it unrealistic.

Attainable Missions work well for building confidence, onboarding users or starting a new habit.

Challenging Missions are useful when someone is ready to improve beyond their usual performance.

Elite Missions should be reserved for ambitious stretch goals that deserve additional recognition.

The best Mission is not always the hardest one. It is the one that creates the right next step.

A public Mission makes the commitment visible and allows colleagues to follow and encourage the user.

Use a public Mission when you want to:

Use a private Mission when the goal relates to:

Private Missions are visible to the user and relevant managers or admins with access to their information.

Visibility should create encouragement, not unnecessary pressure.

Mission Blueprints are ready-to-accept Missions created by managers or admins.

They help users get started without having to decide on every milestone themselves. Relevant Blueprints appear at the top of the Missions discovery area and can be accepted in one click.

Managers and admins can use Blueprints to:

Useful starter Blueprints could include:

Start with one accessible Blueprint and one Blueprint connected to an important team priority. Too many choices can make it harder for users to know where to begin.

Blueprints can be enabled or disabled as team priorities change.

Missions work particularly well as the action layer after a coaching conversation.

At the end of a one-to-one, agree on:

Then turn that agreement into a Mission.

For example:

Before our next one-to-one, create five qualified opportunities, follow up with ten inactive accounts and complete the negotiation training module.

This gives both the user and manager a shared definition of what should happen next. Managers can use Missions to support the priorities discussed during weekly or monthly one-to-ones.

A coaching conversation becomes more valuable when the agreed actions remain visible after the meeting ends.

If your company uses coins, colleagues and managers can boost a Mission by promising coins if it is completed.

Boosting is a way to say:

This commitment matters, and I want to support you.

Managers can boost ambitious coaching goals, while colleagues can support Missions they find inspiring. If the Mission is completed, the user receives the promised coins. If it is not completed, the coins return to the people who boosted it.

Use boosts for:

Coins should add encouragement, not become the only reason to complete the Mission.

When the Mission ends, review more than whether it passed or failed.

Ask:

If the Mission was completed, recognize the effort and identify which behaviour should continue.

If it was not completed, use the result as information. A failed Mission remains visible on the user’s profile, but the user can create another and try again.

Missions should create a continuous cycle:

Choose a focus, commit to actions, track progress, learn and try again.

Start small. A focused Mission with two or three relevant milestones is better than a long checklist.

Make the outcome clear. The user should understand why the Mission matters and what success looks like.

Focus on controllable behaviour. Include actions the user can influence, not only final results.

Connect Missions to larger goals. Daily and weekly commitments should contribute to team targets or personal development.

Use to-dos for actions outside the data. Missions can include coaching, learning, planning and customer work that is not automatically tracked.

Make public Missions encouraging. Visibility should create support and accountability, not embarrassment.

Use difficulty intentionally. Combine attainable Missions that build momentum with challenging Missions that encourage growth.

Use Blueprints to reduce friction. Give users a clear starting point instead of expecting everyone to design a Mission from scratch.

Keep Blueprints relevant. Enable the ones that support the current business priority and disable those that no longer do.

Boost the Missions that matter. Use coins to reinforce meaningful commitments, not every routine action.

Review Missions in one-to-ones. Use the result to recognize progress and agree on the next action.

Encourage users to create their own. Manager-assigned Missions provide direction, but self-created Missions build ownership.

A Mission is a time-bound personal challenge made up of one or more milestones. It helps a user turn a larger goal into specific metrics, achievements or to-do items.

A Mission focuses on an individual commitment and the actions required to complete it. A Competition is generally a broader manager-led initiative where several users or teams compete.

A Mission is primarily a challenge against your own goal. A Battle is a direct head-to-head challenge against another user or manager.

Yes. Users with access to Missions can create a personal Mission without waiting for a manager.

On Pro and Enterprise, managers and admins can create Missions for users within their access scope. A user cannot decline a Mission assigned by their manager or admin.

A Mission Blueprint is a predefined, ready-to-accept Mission created by a manager or admin. It gives users a quick way to take on a recommended challenge without building one from scratch.

No. A Blueprint is accepted as defined by the manager or admin. If it does not fit, the user can create a separate personal Mission instead.

Company admins can create company-wide Blueprints. Managers can create Blueprints only within the teams, departments or cohorts they can access.

The Mission uses the current weekly period and includes relevant activity already recorded earlier in that period.

A Mission can include metrics, achievements and to-do items.

Yes. To-do items are not tracked through connected performance data, so the user must check them off before the Mission period ends.

Difficulty indicates how ambitious the Mission is. The levels are Attainable, Challenging and Elite.

Yes. A Mission can be cloned for another user when the relevant milestones are also available to that person.

Yes. A private Mission is hidden from the wider team but remains visible to the user and relevant managers or admins.

Yes, if coins are enabled. Users and managers who can see the Mission can promise coins that are awarded if it is completed.

The coins are returned to the people who boosted the Mission.

The Mission is shown as failed on your profile. There is no additional penalty, and you can create another Mission and try again.

Managers should use Missions to turn coaching feedback into focused commitments, reinforce individual priorities and follow up on agreed actions.

Admins should create a clear structure for adoption, provide relevant Blueprints and help managers connect Missions to key metrics, onboarding and current business priorities.