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
        • Potential for Sleeper Wallets on Ethereum
  • 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
  • Pick many!
  • We'll get you next time!
  1. Zipwire Collect

Bulk Upload

Here we explain bulk uploading, which aims to save time and effort for your respondent and hopefully increase the speed in which they fulfil your request.

PreviousLifecycle of a CollectionNextDocument Inspection

Last updated 1 year ago

Pick many!

Respondent can pick a load of files to send and we'll figure out what they are and whether they match something that's being collected.

On the Docs tab, where all there stored docs can be seen, they can hit Pick files to get the typical chooser for their operating system. They can select more than one file to upload.

All the files will begin uploading and being processed by our Machine Vision system. This can take a while but it is better than picking and uploading one-by-one on the Open tab.

In the image below, you can see a passport that has been uploaded and processed and has been found to match the passport being sought in a collection request.

We'll get you next time!

If your respondent keeps all their files uploaded and stored in Zipwire, the next time you send them a document request, we'll automatically inspect these files and find matching documents, so they don't have to keep uploading the same stuff.

So if they've ever used Zipwire Collect with you or another business and have their docs already in storage with us, then it'll be quicker for them - and for you!

Seasoned freelancers are likely to have most of their documentation readily available.

๐Ÿšš