Skip to main content
Submissions, a tab of Inbox in the sidebar, is the inbox for your public forms. Every adoption application, foster application, volunteer sign-up, donor form, surrender request and contact form that somebody sends arrives here, whether they filled it in on your public site or on your own website through the embedded form. You build the forms themselves under Settings → Operations & forms → Forms. Each submission is a row: who sent it, which form and their email, the first things they said, what it waits on (Waiting for them to confirm their email, Not in People yet, In People or Became an application) and who it is assigned to. Press the name to open its card beside the list. The card is where a submission is worked: every answer, who it is assigned to, Add to People, the application made from it and the rest, described below. Open full page, at the top of the card, opens the submission on its own page.

Who sees which submissions

A submission is somebody’s details: their name, how to reach them and every answer they gave. So you see submissions only if you can read People, and then only those whose form belongs to a part of RescueConsole you can read. Acting on a submission means marking it, deciding it, assigning it, adding notes and deleting it. Somebody who can read but not write can open a submission but not change it. A role that cannot see People sees no submissions at all, whatever else it holds: an Animal care technician, for example, or somebody signed in only to the Volunteer portal, whose Shifts access is for signing up to shifts.

What arrives, and what happens by itself

When somebody sends a form:
  1. The submission is stored with the status New, and only the answers to questions the form asks are kept. It is in your list straight away.
  2. If the form asked for an email address, that address is sent a link asking whether it was really them. Nothing else happens yet: no person record, no application, no workflow. The visitor is told on screen to look for it.
  3. When they press the link, the rest follows at once. RescueConsole looks for a person with that address in People: if there is one, the submission is joined to them; if there is nobody, a new person record is made from the answers, and the form’s kind gives them a role: an adopter, a foster, a volunteer or a donor. Surrender, contact and general forms add no role.
  4. An adoption, foster or volunteer application also makes the application record for that person, with any animals they ticked on the form.
  5. Any workflow your organization set to start when that kind of form is received starts on the person. See Settings → Operations & forms → Workflows.
  6. The roles and people the form names under Who hears about it are told, and those it assigns are put on it. See Who hears about it.
The card says which way it went: Matched by email to an existing person record or Added to People as a new person record. A person who was already on file keeps the rest of their record as it was: none of the form’s answers are written onto it, because anybody can type an email address into a public form. The one exception is the role, which the application adds, so the person turns up when a coordinator looks for people to review. A submission with no email address is not joined to anybody and has nothing to confirm. Whoever the form names is told about it at once, and it waits on the card until somebody presses Add to People. Why a submission waits A submission is the form as it was sent. Once its sender confirms, the person and any application are made by themselves, and an application leaves this list for Applications. One still waiting with nobody attached says why on its card and its page: Waiting for somebody to confirm A submission waiting on its own sender says so on the card, and so does what is not happening: until it is confirmed, nothing is on anybody’s record and no application exists. You have two ways past it, and the second is often the right one.
  • Send it again puts a fresh link in the post. The previous link stops working.
  • Add to People does the whole thing yourself, and settles the confirmation with it. If you know who applied, because you rang them or you recognize the name, you are a better check than an email is.
Two things can leave a submission waiting with no email sent, and the card says which:
Why it works this way: before this, anybody who could fill in a form could put a person record in your People list, permanently, and a rescue that noticed had to go and delete them one by one. A link nobody clicks is a record you never had to clean up. It also means a mistyped address shows up as a submission somebody can act on, instead of a person record nobody can reach.
Only the roles and people the form names under Who hears about it are told when a submission arrives. The person who sent it sees your form’s thank-you message on screen and, when the form asked for an email address, the link to confirm it, and is sent nothing else unless a workflow you set up sends it. To reply by hand, use Send an email on the card.

The list

Across the top are three numbers: Submissions, Awaiting review (the ones still New) and In spam. Filters The rail on the left narrows the list. Each option shows how many submissions it would give you. The list starts on Application: Not yet. A submission that became an application is that application’s first stage, Received, and it is worked on the application from then on: its answers are on the application’s Answers tab, and the rest of the form’s answers under More from the form. To see those submissions too, choose Became an application, or press the selected option again to see every submission. Above the filters, Views keeps a set of filters you use often.
1

Filter the list

Filter the list.
2

Save the view

Press + Save current view.
3

Name it

Give it a name.
Statuses Deleting several at once
1

Choose the submissions

Tick the box beside each row, or Select all for every row on the page.
2

Delete them

Press Delete selected. You are asked once.
Afterwards a sentence says how many were deleted, how many you did not have the access to delete, and how many were already gone.

Spam

Every public form carries a hidden box that people never see and automated form-fillers fill in. A submission with that box filled in is kept, marked Spam, and left out of the list. It is not joined to a person and starts no workflow. When there is spam, a line above the list says how many were hidden, with Show them. A browser or extension that fills in every box it finds can trip the check on a real person’s application, so look through Spam from time to time. Spam is kept for 30 days, then deleted. Mark a real one Not spam before then. Your site’s forms also show Cloudflare Turnstile, the check that tells a person from an automated sender, usually without asking anything. A submission it does not pass is refused, and the person is asked to reload the page and send it again. The check runs on your rescueconsole.com address. On your own domain, and on a form put on your own website, it is not shown: the hidden box and the limit on submissions an hour from one connection still apply.
  • Spam on a card marks it as spam by hand.
  • Not spam puts a spam submission back to New. You can then add it to People and decide it.
One internet connection can send your forms at most ten times an hour. After that the visitor is asked to try again later.

On a card

Under the person’s name, the line says which form it came from and when. Edit this form, below it, opens that form in Settings → Forms with its questions open. It shows only to somebody who can change forms of that kind.

Answers

What the person told you, in full. The files they sent for a files question are listed under it by name and size; press one to open it. Once the submission is added to People they are documents on the application, or the person, and the answer says so. A files answer cannot be corrected.

Correcting an answer

1

Open the answer

On the submission’s own page, Correct beside an answer opens it to change: a phone number typed wrong, a misspelled email, a date in the wrong box.
2

Type the corrected answer

Type the corrected answer.
3

Save it

Press Save the correction.
It is checked the way the form checks it, so an email still has to be an email and a phone still has to be a phone. An empty answer clears it. The answer is changed where it stands, so adding them to People, the application and a workflow’s merge fields all use the corrected one. What they sent is never lost: under the answer it says Corrected by who and when, and They sent: with what they wrote, or They left it blank. However many times an answer is corrected, what they first sent is the one kept. Correcting the email also changes the address the submission is from, which is the one Add to People matches. The animals they ticked are not corrected here: they are what the person asked about. Add any others under Also about. Correcting needs Change on the area of the form’s kind; somebody who can only read sees no Correct. On a card in the list and on the submission’s own page alike, each answer is shown under the question as the form asks it today, in the form’s order. A long question wraps beside its answer. If a question has since been removed from the form, its answer is kept and shown after the rest, under the name the record gives that field (such as Address), or under its field key when nothing names it. The answer to Which animals are you asking about? names each animal as a link to its record, on the card as on the page. When the form asked which animals the person is interested in, the submission’s own page links each animal to its record.

Add to People

For a submission that is not joined to anybody yet. Add to People makes a new person record from the answers. If an answer is one the person record would refuse, such as a phone with letters in it, nothing is made, and the card says which answer and why, ending “Correct the answer, then add them to People.” On the submission’s page that answer opens to correct, with Correct it; on a card in the list, Correct it on the submission’s page takes you there with it open. A phone is taken however it is written, with brackets, dashes, dots or spaces, as long as it has seven to fifteen digits. The answers go onto the record where they belong: the name, split into its parts when the form asked for the whole thing, the email, the phone, the date of birth, the address, and every question that is a field on the person record. Where the form asked for a part by name, that part is used rather than the split; where it asked for the address as one box, what was typed becomes the first line of the address rather than being guessed apart. If somebody with the same email address is already on file, you are told so instead, with Link to them and Open their record first. Linking joins the submission to that person and does not make a second record. Making a new person needs write on People. Linking to somebody already on file needs read on People. Either way the submission becomes Converted, the workflows set to start when this kind of form is received start on the person, and an adoption or foster form makes its application. Then the application it made opens, so the next step starts there: the submission has left the list it was on, and is under Converted. A surrender request makes no application and is answered on its own page, so you stay on it (or it opens, from the list), with its checklist started. Any other form that makes no application opens the person’s record.

Send an email

Opens Compose addressed to the person, with the conversation linked to this submission. Shown to people with write on Communications. See Compose.

The application

On an adoption, foster or volunteer form, a line shows the application made from it and its stage, with Open the application. The application is where it is approved or denied, and, for an adoption, where the review, the contract and the payment are kept. If you have write on Animals, you can change the stage from the card. When the form is joined to a person but has no application yet, for example because it arrived before applications were made this way, press Make the adoption application, Make the foster application or Make the volunteer application. When nobody is on file yet, the line says the application will be made once they are added to People.

Decision

A submission is not approved or rejected itself. An adoption, foster or volunteer form becomes an application once the person who sent it is in People, and the application is approved or denied: see Approving or denying. So the order is always the form, the submission, the person, the application, and then its workflows. Deciding the application:
  • shows the same decision on the submission, as Approved or Rejected beside its status,
  • marks a New submission Reviewed and takes it off hold, and
  • starts any workflow your organization set to run when this kind of form is approved or rejected, on the person it belongs to, as well as the application’s own.
A submission decided before 4 November 2026, when it could still be decided on its own, keeps its decision. A check on a workflow this form started can still reject it, and its application is denied with it: see Checks.

Assigned to

Who on your team is working on it. Choose somebody under Assign a team member, or press the cross beside a name to take them off. Only members of your team can be assigned, up to ten. Each person newly assigned is told in the app, and by email unless they chose otherwise under Settings → Your account → Profile & password. An adoption or foster form and the application made from it share the same list of people.

Mark reviewed, Spam and Delete

  • Mark reviewed sets the status to Reviewed.
  • Spam and Not spam are described under Spam.
  • Delete removes the submission.
Deleting a submission cannot be undone. The person record it is joined to is kept: deleting removes what they sent, never the person.
Internal notes A line of notes for your team, never shown to the person who sent the form. Press Save to keep them.

The submission page

Open full page on a submission’s card opens its own page, for working one application through, top to bottom.
  • On hold: shown when a check on a workflow this form started has failed and put it on hold, with the reason. Take it off hold clears it. Deciding its application clears it too.
  • Assigned to and Answers, as on the card.
  • Surrender request, on a surrender request: see below.
  • Also about: see below.
  • Emails about this submission: the conversations linked to it, once there is one.
  • The person it belongs to and the application, as on the card.
  • Workflows: see below.
  • Review: Add to People, Mark reviewed, Spam or Not spam, Delete, and the internal notes. Shown to people who can act on the submission.
All submissions at the top goes back to the list. Also about Beneath the answers. The people, animals and organizations your team has added to this submission since it arrived. This is not what the sender told you, and the difference matters. The animals under Answers are the ones the person ticked on the form, and like every answer they never change. Also about is where the second dog they mentioned on the phone goes, or the foster who is keeping the animal, or the vet practice you are waiting on. Each one records who added it. Link a person and Link an animal search your own records. Press the × beside a name to take it off again; nothing happens to the record itself. You need write on the area the form belongs to. Workflows The checklists running for this submission. A workflow runs on a record, not on a submission, so what you see depends on what the submission has become:
  • With an application: the application’s own workflows, the ones this submission started, and the applicant’s workflows for the same purpose, in one list. Start a workflow… offers the checklists for the application and for the applicant.
  • With a person but no application: the person’s workflows.
  • With nobody on file: the workflows that are waiting, with how many steps each has and what starts it. They start once the submission is added to People.
Tick steps here as you would on the record. See Settings → Operations & forms → Workflows for how a checklist is built.

Surrender request

A surrender request is answered here: Accept and record the animal, Taking it, Waitlist or Decline, each with a Note for your team if you like. The note is never shown to the person who asked. The same requests are laid out as a board under Surrender requests. Once answered, the card says who answered and when. Undo takes back a waitlist, a decline or a place held. Accepting is final, because the animal is on its record by then: the card links to it.

Its checklist comes first

When a workflow started from the request, such as the standard A surrender request arrives, Accept and record the animal (and Take Biscuit back) waits until that checklist’s required steps are done. The card names the ones left, under Its checklist comes first, and Workflows further down the page is where you tick them. A step that is ticked by the answer itself, like the standard checklist’s Decide what you can offer, is not waited on: answering the request in any way (accepting, holding a place, waitlisting or declining) ticks it. Taking it, Waitlist and Decline never wait. A checklist like this starts on the person, so when nobody is on file for the request yet, the card says to Add to People first: that is what starts it.

Adopted from you

When the request is for an animal your rescue adopted out, the card says so before anything else: the animal, when and to whom it was adopted, and what matched (the microchip number on the request, the adopter’s email, or both). Its button names the animal (Take Biscuit back, for Biscuit). Pressing it reverses that adoption and records the animal’s return on its own record, putting it back in your care, rather than adding a second animal. The note becomes the reason for the reversal.

Sharing it with other rescues

When you cannot take the animal and the person agreed to their request being shared, the card has Share with partners and Share with all rescues. See Shared surrenders for who it reaches, what they see, and what happens when one takes it.