Zipwire Documentation
Visit Zipwire
  • ๐Ÿ‘‹Welcome to Zipwire
  • Overview
    • ๐Ÿ’กWhat is it?
    • ๐Ÿ™‹โ€โ™€๏ธWho can use it?
    • โœจOur Features
    • ๐Ÿš—Can I test drive it?
      • ๐Ÿ“ฆSetting up Zipwire Approve
      • ๐Ÿ“ฅSetting up Zipwire Collect
    • ๐Ÿ”‘Logins & Invitations
    • ๐ŸขZipwire Collect: Rapid Onboarding, Effortless Compliance
    • ๐Ÿ’พData Ownership in Zipwire
  • Zipwire Approve
    • ๐Ÿ…How Zipwire Approve is radically different and speeds up pay day
    • โ›”Why we don't track start and end times
    • ๐Ÿ“ฆUnboxing key concepts
      • ๐Ÿ“œAccounts
      • โฒ๏ธTimesheets
      • ๐Ÿ‘ทSenders
      • ๐ŸšฆApprovers
      • ๐Ÿ‘‘Processors
      • โคต๏ธWorkflows
      • ๐Ÿท๏ธAssignments
      • ๐Ÿ“Billing Plans
      • ๐Ÿ’ฑRate Plans
      • ๐Ÿ“ฌTeams & Inboxes
      • ๐ŸขWorkplaces
      • ๐Ÿ›ก๏ธClients
      • โœ๏ธThe Journal
      • ๐ŸคธActivities
      • ๐Ÿ’ธPayment Methods
    • ๐Ÿ”ฒLogical structure
    • ๐Ÿ› ๏ธSet up your workplace
    • ๐ŸšฅProcessing stages
    • ๐Ÿ’ตUnderstanding invoicing
    • ๐Ÿท๏ธUsing assignments
      • ๐Ÿ–๏ธHoliday assignment
  • Zipwire Collect
    • ๐Ÿ—„๏ธEffortless Document Collection for Any Need
    • ๐ŸŸขGet Started
    • ๐Ÿ˜ญIDSP, IDVT, KYC, KYB and AML
      • ๐ŸคณSelfie Checks Powered by Yoti
      • โ›“๏ธBlockchain Attestations
    • ๐Ÿ“„Using Packs
    • ๐Ÿค–Machine Vision
      • ๐ŸคทFailure to Recognise
      • ๐ŸชชDocument Types
    • โœ๏ธManual Entry for Streamlined Information Gathering
    • โœจCreating a Collection with AI
    • ๐Ÿ‘€What the Respondent Sees at Their End
    • โ™ป๏ธLifecycle of a Collection
    • ๐ŸššBulk Upload
    • ๐Ÿ”Document Inspection
  • Fundamentals
    • ๐Ÿ›ก๏ธSecurity
      • ๐Ÿ“ฒAuthenticator mobile apps
      • ๐Ÿ”Two factor in Zipwire
      • Wallet Connections
      • Sign-in with Ethereum
      • Attestations
        • The "IsAHuman" Attestation: Purpose and Limitations
        • Zipwireโ€™s Master Attester Wallet Address and Public Key
      • Wallet Verification Guide
        • Introduction to Sleeper Wallets and Blockchain Legends
        • How Sleeper Wallets Are Created
        • Verifying Attested Wallets
        • The Market for Selling and Buying Attested Wallets
        • Holistic Evaluation of Ethereum Wallets
        • The Future of Attestations and Wallet Verification
        • Verifying Zipwireโ€™s Merkle Root Attestations for Developers
      • Understanding Merkle Trees and Proofs
  • Use Cases
    • ๐ŸŽญIdentity Checks - Right to Work
    • ๐ŸชชCompliance - Know Your Customer
    • ๐ŸŽจFor Senders
      • ๐Ÿ’ฌSending journal updates via WhatsApp
      • ๐Ÿคธโ€โ™‚๏ธNaming activities
      • โœ๏ธTracking time in your Journal
      • โฒ๏ธSend your first timesheet
    • ๐Ÿ“ฑTracking time via WhatsApp
    • ๐Ÿ–ฅ๏ธFor Approvers
      • ๐Ÿ’ฌApproving timesheets via WhatsApp
  • Troubleshooting
    • ๐Ÿ”€Tangled Identities
Powered by GitBook
On this page
  • Enabling WhatsApp
  • Sending a journal update
  1. Use Cases
  2. For Senders

Sending journal updates via WhatsApp

Zipwire has a WhatsApp bot that can accept plain English descriptions of what you've been working on.

Enabling WhatsApp

Before we can accept journal update messages, Zipwire needs to be sure of the mobile phone number you use for WhatsApp.

There are two ways to prove your phone number is really you.

  1. You tell us your number, we send a short code via WhatsApp, and you confirm the code on our website.

  2. You send a special Connect message with a longer code to the Zipwire bot via WhatsApp and if we recognise the code, we hook you up.

To try either of these, head to My account and the Devices tab.

Sending a journal update

The Zipwire bot needs to be able to tell the difference between messages and figure out how to treat them; whether they journal updates or something else.

To send a journal update, start the message with any of the following, then continue to describe what you did.

  • "This week"

  • "Last week"

  • "Week 1" where 1 can be any week number in the recent past

  • "Today"

  • "Yesterday"

  • "Tomorrow" yes, you can tell us what'll you're planning to do

The bot will use all your current activities when understanding your message, so use the same wording and acronyms.

If the bot thinks you're talking about an entirely new activity, it will go ahead and create it, then log time against it. This activity will not be linked to a workflow so you'll be asked to link it when you later come to create your timesheets.

Some examples might be:

"This week I worked full time on ABC"

"Today I worked on Project Alpha half the day and the rest on Research"

"Yesterday I did 2 hours for Mike and 4 hours at the Kumars"

PreviousFor SendersNextNaming activities

Last updated 1 year ago

๐ŸŽจ
๐Ÿ’ฌ