04 / For business
Ask for a response.Keep what comes back.
Add a signature, form, or document request to the item you send. The recipient completes it in Keepable, and their response comes back with who sent it, when it was sent, and the original request beside it.
Forms · document requests · bank statements · utility bills · CAC certificates · ID pages
In the app
One request, going out
Account refresh · 1,400 customers
- What you asked for
- Where they answer
- What comes back
- What you can see
-
Ask
You ask once and it reaches everybody
The same request goes to one customer or to fourteen hundred, and each one is addressed to a verified person rather than broadcast to a list. Nobody is filling in a PDF on a phone and photographing it back.
-
Receive
You get files whose history you can actually see
When a customer sends back a document that Keepable delivered to them in the first place, its provenance travels with it. You are looking at the bank's own statement, not a screenshot of one.
-
Chase
You can see who has not answered, without asking
Outstanding is a list, not a guess. You can send a reminder to the people who have not answered rather than to everybody, which is the difference between a nudge and a nuisance.
The document you are asking a customer for is usually one they already keep here.
- What you can ask for
- Seven kinds of question, including a file upload, plus a signature on the document itself.
- What comes back
- The answers and the files, sealed, with the time they were sent.
- What you can see
- Who has answered, who has not, and when each one arrived.
The detail
- What kinds of question can a form ask?
- Seven: a short answer, a long one, pick-one, pick-many, a number, a date, and a file upload. Pick-one and pick-many can branch the rest of the form, so somebody who says they rent is not asked about a mortgage. An upload question carries your own instruction, so it reads "a statement covering the last six months" rather than "attach a file".
- What can they actually upload, and how big?
- PDF, JPEG, PNG or GIF, up to 20 MB each, and you can narrow that to the one type you want. A single form takes at most five upload questions, which is a deliberate ceiling: past that you are not collecting a document, you are running an application, and it should have been more than one request.
- What if I have to collect a NIN, a BVN or an account number?
- Mark the question for what it holds and the handling follows. It is stored encrypted rather than in the clear, kept out of the search index, masked everywhere it is displayed, and left out of exports unless somebody with the right to see it asks for it, which is itself written to the record.
- How do I get the answers into my own systems?
- A CSV, one row per person, leading with the person and then your own reference for them, so it joins straight back to the customer record you already hold. Files come through as identifiers you fetch rather than as attachments in a spreadsheet.
- How do I know the statement they sent me is real?
- If it came from Keepable in the first place, it still carries the seal of the organisation that issued it, and that travels with it into your hands. If they uploaded it themselves, you can prove they uploaded that exact file at that exact time, and nothing about where it came from. The two look different, deliberately, so nobody has to guess which they are holding.
- How do I chase the ones who have not answered?
- Outstanding is a list you can read, not a number you infer, and it names the people. You send the reminder to them rather than to the whole fourteen hundred.
The limit
A request is a request. Keepable will not make somebody answer, and it does not verify the contents of what they send: if a customer uploads a bank statement, we can prove they uploaded that file and when, not that the balance printed on it is real. Where the document came from Keepable in the first place, that is a different matter, and the difference is visible to you.
Start here
For developers: Responses reference.