@jobber/components-native 0.105.2 → 0.105.4-addeditor-cab44cf.11

package/dist/docs/voice-and-tone/voice-and-tone.md

@@ -0,0 +1,385 @@
+# Voice & tone
+
+If you work with Jobber — whether you're writing product copy, designing an
+interface, building an AI feature, or crafting a marketing email — there's a
+good chance you're speaking on behalf of the brand. To make sure we all sound
+like the same Jobber, we have guidelines for voice and tone.
+
+Our **voice** is our personality. It's consistent, recognizable, and doesn't
+change regardless of who we're talking to or what we're building. Our **tone**
+is how we apply that voice in a given moment. It shifts based on context and
+audience, but it always operates within the boundaries the voice sets.
+
+Think of it like this: you're the same person whether you're talking to a new
+client or a longtime friend. Your personality doesn't change, but how you
+express it does.
+
+This document covers the foundational layer: what Jobber's voice is, how tone
+works as a system, and the principles that apply everywhere. Audience-specific
+guidance builds on this foundation and lives separately.
+
+## Jobber's voice
+
+Jobber's voice is confident and direct, but never cold. We're loyal to our users
+and hungry for their success, and that comes through in everything we write.
+We're not especially cute, gentle, or goofy. There's a time and place for that,
+but we're here to help people run better businesses, and our voice reflects
+that.
+
+We're also a collaborator, not just a tool. That means we show up with relevant
+knowledge when it's needed, back users up when they're busy, and earn trust by
+being consistent and transparent. We never make users feel talked down to, and
+we never make them feel like they're on their own.
+
+If something sounds stiff or unnatural out loud, it's probably not in our voice.
+
+In practice, that means:
+
+* **Lead with what matters.** Don't make people work to find the point.
+* **Use the simplest word that does the job.** Never use jargon to sound
+  credible.
+* **Be direct without being blunt.** Say what you mean, but stay human about it.
+* **Show the work, not the complexity.** If something happens behind the scenes,
+  say what it did, not how it did it.
+* **Don't perform positivity.** Sincerity lands better than enthusiasm.
+* **Meet frustration with honesty and a clear path forward.**
+
+## Our priorities
+
+When writing for Jobber, two things should always be true.
+
+**Clarity first.** Every word should earn its place. If a message isn't
+immediately understood, it isn't doing its job. Pick one thing to say and say it
+well.
+
+**Empathy always.** Put yourself in the user's position. What are they trying to
+do right now? What do they already know? What would make this moment harder or
+easier? Let those answers shape what you write.
+
+Tone, energy, and detail level all follow from these two.
+
+## Tone
+
+Our voice stays constant. Our tone adapts.
+
+In product, tone shifts based on two things: the context the user is in, and
+where they are in their journey with Jobber. Getting both right is the
+difference between copy that feels generic and copy that feels like it was
+written for this moment and this person.
+
+## Getting started
+
+This is often the first time a user encounters a feature or flow. It's a moment
+of potential — they're here because they want to do something. Don't waste it
+with technical explanations or feature descriptions.
+
+**Lead with the action.** Start with a verb. The user should know what to do
+before they know why.
+
+**Front-load the value.** Put the most important information first. Users scan
+before they read — if the value isn't in the first few words, it may not land at
+all.
+
+**One idea at a time.** Don't bundle multiple instructions or benefits into a
+single message. If there's more to say, expose the steps without explaining them
+all upfront. Take it one at a time.
+
+**Keep it short.** Aim for one sentence. Two at most.
+
+**Avoid technical language.** Write for someone encountering this for the first
+time. If a word needs explaining, replace it.
+
+| ✅ **Do**                                     | ❌ **Don't**                                                               |
+| -------------------------------------------- | ------------------------------------------------------------------------- |
+| Add your first client to get started         | The client management module allows you to store and organize client data |
+| Set up your schedule to start booking jobs   | Welcome to the scheduling feature                                         |
+| Create a quote to start winning work         | Quote creation is now available                                           |
+| Connect your bank account to get paid faster | Payment integration setup required                                        |
+
+## Taking action
+
+The user is focused and moving. Copy should serve the action, not compete with
+it. Keep it minimal when the task is clear. Add context only when the
+consequences aren't obvious or the stakes are high.
+
+**Use active voice.** The user is the subject. They do things — things don't
+happen to them.
+
+**Be specific.** Generic labels create doubt. Tell the user exactly what will
+happen when they act.
+
+**Lead with a verb.** Button labels should start with an action word and use
+title case. No punctuation.
+
+**Match the weight of the action.** A routine task needs a short label. A
+significant or irreversible action warrants a brief line of context — enough to
+feel considered, not alarming.
+
+**Never use filler labels.** Vague labels like "Click here" or "OK" tell the
+user nothing. Even "Submit" on its own is ambiguous — "Submit Documents" or
+"Submit Request" is always clearer. Every label should be meaningful on its own.
+
+**Active voice applies to everything.** Not just buttons — confirmations,
+instructions, helper text, error messages. If Jobber is doing something, say
+"we." If the user is doing something, say "you." Passive voice creates distance
+and ambiguity.
+
+| ✅ **Do**                                     | ❌ **Don't**                   |
+| -------------------------------------------- | ----------------------------- |
+| Send Quote                                   | Submit                        |
+| Schedule Job                                 | OK                            |
+| Add Line Item                                | Click here                    |
+| Save Changes                                 | Yes                           |
+| Delete Client                                | Click here to proceed         |
+| Submit Documents                             | Submit                        |
+| Your quote has been sent to Sarah            | The quote was sent            |
+| We drafted this quote based on your last job | A draft has been generated    |
+| You haven't added any line items yet         | No line items have been added |
+
+## Success
+
+Most success states are routine. A job was scheduled, a quote was sent, changes
+were saved. Acknowledge it clearly and move on. Users don't need enthusiasm —
+they need confirmation.
+
+**Be brief and specific.** Say what happened. Don't editorialize.
+
+**Don't over-celebrate the ordinary.** Completing a normal workflow isn't an
+achievement. Treating it like one feels hollow and, over time, erodes trust.
+
+**Save celebration for milestones that actually matter.** First job booked,
+first payment received, hitting a revenue goal — these are moments worth
+marking. Celebrate the user's achievements, not Jobber's processes. Completing a
+sync or finishing a setup step is Jobber doing its job, not the user doing
+theirs.
+
+### Routine acknowledgment
+
+| ✅ **Do**                  | ❌ **Don't**                              |
+| ------------------------- | ---------------------------------------- |
+| Quote sent to Sarah       | Quote sent successfully!                 |
+| Job scheduled for Tuesday | Great job! Your job has been scheduled!  |
+| Changes saved             | Done! Everything's saved and good to go! |
+
+### Success with additional context
+
+Sometimes completing an action unlocks something new. When it does, use the
+moment to tell the user what's most relevant to them right now — not everything
+that's changed, just what matters most in that moment.
+
+| ✅ **Do**                                                       | ❌ **Don't**                        |
+| -------------------------------------------------------------- | ---------------------------------- |
+| Jobber Payments is set up. You can now accept payments online. | Integration successful! Great job! |
+
+### Milestone moments
+
+| ✅ **Do**                                                   | ❌ **Don't**                          |
+| ---------------------------------------------------------- | ------------------------------------ |
+| Congrats, you've booked your first job.                    | Woohoo! First job unlocked! 🎉       |
+| Milestone achieved: $100k in revenue this year. Nice work. | Amazing work! You're a superstar! 💰 |
+| Your first payment just came in. That's a big deal.        | 🎉 You got paid! Congrats!!          |
+| 100 jobs completed. You're building something real.        | 100 jobs! You're on fire! 🔥         |
+| Your first 5-star review. That's what it's all about.      | Woohoo! Someone loves you! ⭐⭐⭐⭐⭐     |
+
+## Guidance
+
+Good guidance is invisible. Users shouldn't notice it — they should just feel
+like the product is easy to use. That means offering help at the right moment,
+in the right amount, and then stepping back.
+
+**Only guide when it adds something.** If the UI makes the next step obvious,
+don't add text just to fill the space. Unnecessary guidance creates noise and
+teaches users to ignore it.
+
+**Be specific.** Generic instructions tell the user nothing they couldn't
+already see. Guidance should relate directly to what the user is trying to do
+and why it matters.
+
+**Don't repeat the label.** Helper text exists to add context, not echo what's
+already on screen. If a field is labelled "Business Name", the helper text
+shouldn't say "enter your business name."
+
+**Let the component and the moment guide you.** A tooltip is a quick answer to a
+specific question. Helper text adds context before someone acts. An empty state
+orients someone who has nothing to work with yet. Each has a different job —
+match what you write to that purpose, not to how much space you have.
+
+**Headlines and body copy work together, not in parallel.** The headline carries
+the main idea. Body copy adds context that the headline can't. If you find
+yourself repeating the headline in different words, you don't need body copy.
+Every line should earn its place.
+
+| ✅ **Do**                                                                         | ❌ **Don't**                                                                               |
+| -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
+| **Get paid faster** / Accept card payments directly from quotes and invoices.    | **Get paid faster** / Get paid faster with Jobber Payments.                               |
+| **New in scheduling** / You can now drag and drop jobs directly on the calendar. | **New in scheduling** / We've made some improvements to the scheduling feature in Jobber. |
+
+### Empty states
+
+| ✅ **Do**                                                                 | ❌ **Don't**           |
+| ------------------------------------------------------------------------ | --------------------- |
+| No jobs scheduled yet. Add your first job to get started.                | No data to display    |
+| You haven't added any team members. Add someone to start assigning jobs. | No team members found |
+| No clients yet. Add your first one to start sending quotes.              | Nothing here yet      |
+
+### Helper text
+
+| ✅ **Do**                                                          | ❌ **Don't**              |
+| ----------------------------------------------------------------- | ------------------------ |
+| This is the name your clients will see on quotes and invoices.    | Enter your business name |
+| Add your hourly rate so we can calculate job costs automatically. | Enter a number           |
+| Choose how far you're willing to travel for a job.                | Set your service area    |
+
+### General body copy
+
+| ✅ **Do**                                                                                     | ❌ **Don't**                                                                                        |
+| -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| Turn on automatic reminders to follow up with clients who haven't responded to a quote.      | This feature allows you to configure automated reminder functionality for outstanding quotes.      |
+| Your team can see their schedule, update job status, and log time — all from the mobile app. | The mobile application provides team members with access to various job management capabilities.   |
+| Connect Jobber to QuickBooks Online to keep your books up to date without the double entry.  | This integration enables synchronization between Jobber and QuickBooks Online accounting software. |
+
+## Errors
+
+Something has gone wrong. This is not the moment for technical language, humor,
+or vague reassurance. Users are frustrated or confused — meet them with clarity
+and a way forward.
+
+**Explain what happened in plain language.** You don't need to surface the
+technical cause, but you do need to tell the user what went wrong in terms that
+mean something to them.
+
+**Always give a path forward.** An error without a next step leaves the user
+stuck. Even if the fix is outside Jobber's control, tell them what to do.
+
+**Don't blame the user.** Focus on the fix, not the fault. "That email address
+is already in use" is better than "you entered a duplicate email."
+
+**Don't be vague to avoid being technical.** "Something went wrong" on its own
+is not helpful. Be as specific as the situation allows.
+
+**Be human, not dramatic.** Errors are frustrating enough without the product
+making them feel worse. Stay calm, stay clear.
+
+| ✅ **Do**                                                                    | ❌ **Don't**                                                                        |
+| --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
+| We couldn't save your quote. Check your connection and try again.           | An error occurred while attempting to save the record. Please retry the operation. |
+| That email address is already linked to an account. Try signing in instead. | The value entered in the email field already exists in the system.                 |
+| We couldn't process your payment. Check your card details and try again.    | Payment processing failed due to an invalid response from the payment gateway.     |
+| Something went wrong on our end. Try again or contact support.              | Whoopsie! The servers are taking a little nap. Try again soon! 😴                  |
+
+## High stakes moments
+
+When an action is irreversible or has significant consequences, say so clearly.
+Don't soften it to the point of ambiguity and don't dramatize it to the point of
+panic. Just be direct about what's about to happen.
+
+**State the consequence, not just the action.** "Delete" on its own isn't
+enough. Tell the user what they'll lose.
+
+**Don't bury the risk.** The consequence should be the first thing the user
+reads, not a footnote.
+
+**If something can't be undone, say so.** Don't leave users to assume the
+consequences. A single clear line — "This can't be undone" — is better than
+silence.
+
+**Give a genuine out.** Cancel should always be an option, and it should be easy
+to find.
+
+**When a headline is present, let it name the action. Use the body to state the
+consequence.**
+
+| ✅ **Do**                                                                                                                     | ❌ **Don't**                                                                                          |
+| ---------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
+| **Delete client** / Sarah Johnson and all her jobs, invoices, and history will be permanently removed. This can't be undone. | **Are you sure?** / Are you sure you want to delete this client? This action will delete the client. |
+| **Cancel your plan** / Your team will lose access at the end of your current billing period.                                 | **Cancel plan** / Canceling your plan will cancel your plan and all associated features.             |
+| You're over your team member limit. Purchase additional members or upgrade your plan.                                        | User limit exceeded. Please review your subscription.                                                |
+
+## AI insights
+
+Jobber AI has access to two things most tools don't: knowledge of your business
+and knowledge of the industry. A good insight draws on both. A generic one
+wastes the moment.
+
+**Be specific to the user.** An insight that could apply to anyone adds no
+value. Ground it in what Jobber actually knows — their clients, their jobs,
+their patterns.
+
+**Ask before acting.** Where an action has consequences, check in first. A
+prompt that says "want me to handle this?" respects the user's autonomy. One
+that acts without asking undermines it.
+
+**Surface yourself at the right moment.** An insight offered mid-task is an
+interruption. One offered at a natural pause is a collaborator checking in.
+
+**Say less.** If it takes more than two sentences to explain an insight, it
+probably isn't ready to be surfaced yet.
+
+| ✅ **Do**                                                                            | ❌ **Don't**                                                                     |
+| ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
+| You haven't followed up with 3 clients since last week. Want me to send a reminder? | Jobber AI has detected potential follow-up opportunities in your client list.   |
+| Jobs like this one usually take 2 hours. Want to update the estimate?               | Based on historical data analysis, your time estimation may require adjustment. |
+| Brian typically prefers morning appointments. Want to schedule accordingly?         | Customer preference data suggests scheduling optimization may be beneficial.    |
+
+## Motivation
+
+Jobber's users are building something. There are moments in the product where
+acknowledging that progress genuinely matters — not as a default tone, but as a
+response to something real happening in their business.
+
+**Identify the moment.** Motivation is earned, not assumed. The right moment is
+one where the user has done something meaningful — hit a milestone, made a
+decision, or is close to achieving a goal. Generic encouragement feels hollow.
+Specific acknowledgment feels human.
+
+**Match the energy to the moment.** A user closing in on a revenue goal deserves
+more than a neutral confirmation. A user completing a routine task doesn't need
+a pep talk.
+
+| ✅ **Do**                                             | ❌ **Don't**                            |
+| ---------------------------------------------------- | -------------------------------------- |
+| You're $2k away from your revenue goal. Keep going.  | Great job completing your tasks today! |
+| 10 quotes sent this week. That's your best week yet. | You're doing amazing! Keep it up! 🌟   |
+
+### Humor
+
+A light touch can make Jobber feel human, but only when the moment genuinely
+calls for it. Warmth and humor are not the same thing — a well-timed observation
+that shows Jobber is paying attention will always land better than a joke.
+
+Never use humor when a user is frustrated, confused, or at risk of losing
+something. And never let it get in the way of clarity.
+
+**In AI interactions**
+
+These examples rely on Jobber knowing enough about the user to feel genuine
+rather than generic.
+
+| ✅ **Do**                                                | ❌ **Don't**                                        |
+| ------------------------------------------------------- | -------------------------------------------------- |
+| Still at it at 11pm. Let's get this done quickly.       | Burning the midnight oil! You're a rockstar! 🌟    |
+| Quiet week — looks like you've got some breathing room. | Wow, not many jobs this week! Hope things pick up! |
+
+## Technical rules
+
+For full guidance on capitalization, punctuation, spelling, pronouns, dates, and
+numbers, see [Formatting](../formatting/formatting.md). A few reminders on the rules
+that most directly affect voice and tone:
+
+* **American English spelling.** Labor, not labour. Customize, not customise.
+* **Use "you" and "we".** Address users as "you". Refer to Jobber as "we". Avoid
+  referring to Jobber in the third person.
+* **Oxford comma.** Use a comma before "and" or "or" in a list. "Jobs, quotes,
+  and invoices" not "jobs, quotes and invoices."
+
+A few additional rules not covered in formatting:
+
+**Use active voice.** Covered in taking action, but it applies everywhere. If
+you find yourself writing "was" or "has been", check if active voice would be
+clearer.
+
+**Avoid absolute statements.** Don't make promises you can't keep. "Always",
+"never", "guaranteed" set expectations that erode trust when they aren't met.
+
+**Use contextual links.** Link meaningful words or phrases, not "click here" or
+"read more". The link text should make sense on its own.

package/dist/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@jobber/components-native",
-    "version": "0.105.2",
+    "version": "0.105.4-addeditor-cab44cf.11+cab44cfa",
     "license": "MIT",
     "description": "React Native implementation of Atlantis",
     "repository": {
@@ -71,7 +71,7 @@
     "devDependencies": {
         "@babel/runtime": "^7.29.2",
         "@gorhom/bottom-sheet": "^5.2.8",
-        "@jobber/design": "0.102.0",
+        "@jobber/design": "0.103.1-addeditor-cab44cf.11+cab44cfa",
         "@jobber/hooks": "2.21.0",
         "@react-native-community/datetimepicker": "^8.4.5",
         "@react-native/babel-preset": "^0.82.1",
@@ -122,5 +122,5 @@
         "react-native-screens": ">=4.18.0",
         "react-native-svg": ">=12.0.0"
     },
-    "gitHead": "c76d3cfd8af83d2700a0e78c3bc2fc549771a471"
+    "gitHead": "cab44cfa1430ab6784636b2d3db8ad771db0999a"
 }