The application process
Why did my application go unanswered?
You filled in the form, an application received email arrived, and then silence. Three weeks on, no rejection and no invitation. Here we explain where that silence comes from through the mechanics of GoTeam itself: which status change produces an email for the candidate, which does not, and who decides to send it.
3 statuses
A ready status email template exists only for Under Review, Accepted and Rejected
5 buttons
The statuses an application can be moved to in the panel: Pending, Under Review, Interview, Accepted, Rejected
7 days
An application sitting in Pending or Under Review beyond this period lands on the attention list in the panel
Hearing nothing back has no single meaning. A change in the status of an application and an email reaching you are two separate actions. In GoTeam, even when the status changes in the panel, the decision to send the email belongs to the hiring team, and the company notification setting has to be on as well. A ready status email template exists for three statuses only: Under Review, Accepted, Rejected.
Silence is not a decision, it is a gap
Looking at an unanswered application, the natural assumption is this: somebody read it, decided against it, and could not be bothered to say so. That is mostly not how the mechanics work. An applicant tracking system holds two separate events, and one does not have to trigger the other: the status of the application changing, and an email reaching you. The first happens by pressing a button in the panel, the second asks for its own confirmation.
On the GoTeam side that split sits plainly in the code. The person changing a status meets two buttons: update only, and send email. The status changes either way, the only difference is whether anything reaches you. When the company notification setting is off, the second button never appears; a single update status button is left, and the dialog says no notification will be sent to the candidate.
What is described here is only how GoTeam behaves. If the company you applied to uses another system, the setup there may differ and we have no measurement of those systems. Even so, seeing the inside of one system makes the same silence easier to read.
- A status change and a notification going out are two separate actions. The second is not a consequence of the first, it is its own decision.
- Only three of the five statuses have a ready email template for the candidate. On the remaining two the system finds no template and skips the sending step.
- AI changes the status of no application on its own. It ranks and it flags; the action that changes a status always runs under a user identity.
Which box your application is sitting in
The schema holds eight application statuses, three of them belonging to life after the hiring decision. The five that concern you as a candidate, and that appear as buttons in the panel, are these: Pending, Under Review, Interview, Accepted, Rejected. The moment your application is received it opens in Pending.
The table writes next to each status whether a ready email template for the candidate exists. Having a template does not mean the email will go out; not having one means it will not. The template gate comes first, the choice gate second.
| Status in the panel | What it means | Ready email template |
|---|---|---|
| Pending | The record was opened, the CV analysis started in the background, nobody changed the status. | None. The application received notice is a separate template, attempted at the moment of the record. |
| Under Review | The application is being read or has been set aside to be read. | Yes: the status update template. |
| Interview | The application was moved to the interview box. | None. This status produces no status email for the candidate; the interview invitation goes out from a separate module. |
| Accepted | A positive decision was made, and document and detail requests can be tied to this candidate. | Yes: the acceptance template. |
| Rejected | The process is closed for this application. | Yes: the rejection template. |
The Interview status and an interview invitation are not the same thing
Your application may have been moved into the Interview box in the panel while nothing at all reached you. Those are separate events: a status change moves the application record, an interview invitation goes out from its own family of templates (invitation, date change, cancellation, reminder). Neither triggers the other.
There is a plan difference too. Every plan can use the Interview status, while interview scheduling and invitation emails are open only on the Professional and Enterprise plans. In the setup of the company you applied to, the interview box may be full while no invitation email is ever produced; the contact is made by phone or through an email written by hand.
What is happening to an application sitting in Pending
There is no status email to send for an application sitting in Pending, because nothing has changed. The silence here corresponds not to a decision but to a decision not yet made. The panel does not leave that invisible either: applications sitting in Pending or Under Review for more than 7 days land on a separate counter and an attention list, oldest first, at most 12 rows. That is a signal, not a guarantee; reading the list is up to the hiring team.
When a status really does change, the work finishes in a single database transaction: the record is updated, the audit trail is written with the old value, the new value and the user who made the change, and a domain event is produced. That is not a notification going out to you, it is an internal record kept so the company can read the process back later.
On the candidate side there is no portal or login screen where you could see that record. In GoTeam the surfaces a candidate opens through a link are interview questions, document upload, returned documents and detail updates. The way to learn your status is the emails that reach you, and asking the company directly.
The three gates that decide whether an email goes out
For a status change to produce an email for you, all three gates have to be open. If one is closed, the status still changes and you still see nothing. The order is this: the status has to have a template, then the person changing the status has to choose to send, then the company notification setting has to be on.
The first gate is the quietest. On a status change the system first looks for the template type matching that status. A type comes back for acceptance, rejection and review; on the remaining statuses the function returns nothing and the sending step never runs. That is why the Interview and Hired statuses produce no status email for the candidate.
The other two gates sit in the setup and the preference of the employer. Nothing on the candidate side affects them. What knowing this is good for is not reading the silence as a signal about yourself.
The second gate: was sending chosen
The person changing the status sees two buttons, and the choice is made there. Choosing update only moves the application to its new status and sends you nothing. The server side is built the same way: an email is only attempted when sending was marked on the request and the status genuinely changed.
The rule is the same on a bulk action. An error during sending does not roll the status change back: the email runs as a best effort, and the status of the application does not depend on it.
The third gate: the company notification setting
If the company email notifications setting has been switched off, the system falls back to a provider that sends nothing: no email goes out and the record is logged as skipped. That setting covers the whole of sending rather than individual templates, the application received notice included. Its default is on. In a setup where it is off, the panel shows a single button and states that no notification will be sent, so the decision is made knowingly.
When all three gates are open, one safeguard steps in. The send key is built from the company, the application, the old status, the new status, the template type and the update time before the transition; if the same transition is triggered a second time, the send is deduplicated. So if the same outcome reached you twice, that is not a repeated notification, it is genuinely two separate status changes.
Explanations other than being ignored
Part of the silence is produced not at the decision stage but before it. Everything below has a counterpart in the GoTeam code. All of it is about the application itself, not about your CV.
| What you experienced | Its counterpart in the system |
|---|---|
| The application received email never arrived | That email is attempted at the moment of the record and its failure is swallowed silently. Not receiving it does not mean the application was not saved. |
| The link of the posting you applied to no longer opens | When a posting comes off the site the page returns a 404. Nothing happens to existing applications, the record stays where it is. |
| You submitted the form but got an error | A submission to a posting past its deadline or already closed is rejected. In that case the application may never have been created. |
| You applied to the same posting twice and nothing changed | A second application arriving from the same email within 24 hours is rejected. Sending again does not move the application forward. |
| The posting closed but no rejection reached you | Nothing automatic ties the closing of a posting to application statuses. Closing on its own produces no rejection. |
An application that was not rejected stays in the pool
Your application does not stay tied only to the posting you applied to. An employer can search the whole pool, and you can end up in the results for a position you never applied to. Hearing nothing back does not mean the record is closed.
The reverse holds too: rejected candidates are removed from the default results of a pool search. The excluded statuses are Hired, Rejected, Terminated and Withdrawn. Even when a rejection never reaches you as an email, that record stays out of later searches.
Where AI sits in all of this
The CV analysis starts in the background for every application, and the application request does not wait for it to finish. Even if the analysis is delayed, the application record stays where it is. What it produces is a ranking and an evidence list, not a decision.
AI changes the status of no application on its own, and it gives no score either: item by item it answers whether something is evidenced in this CV, leaves a verbatim quote from the CV next to its answer, and the arithmetic is done in code. An item with no evidence does not count as half a point, it leaves the denominator. The system does not learn from past hiring outcomes either; who was invited before never enters scoring.
Frequently asked questions
No, it cannot be read that way directly. On the GoTeam side the move to the rejected status does have a ready email template, but whether it is sent depends on the choice of the person changing the status and on the company notification setting. The same silence can just as well come from the application still sitting in Pending. There is no way to tell the two apart from the outside; the clearest route is asking the company directly.
GoTeam has no portal or login screen where a candidate can see their application status. The surfaces a candidate opens through a link are interview questions, document upload, returned documents and detail updates. Status information reaches you only through the emails that are sent, and only when the three gates above are open.
It does not. A second application sent to the same posting from the same email address within 24 hours is rejected and no new record is created. The order, the date and the status of the existing application do not change. Instead of trying again, it helps to make sure the first application was recorded.
No. When a posting comes off the site the page returns a 404, and that is only about whether the page opens. Applications already sent stay where they are, their status does not change and they keep showing in the panel. Nothing in the code ties the closing of a posting to rejecting its applications.
Because moving to the Interview status produces no status email for the candidate. The system finds no template for that status and skips the sending step. An interview invitation goes out from a separate module with its own templates; interview scheduling is also only open on the Professional and Enterprise plans. The two events do not trigger each other.
No. AI changes the status of no application on its own and eliminates nobody by itself. What it produces is a ranking and an evidence list. The action that changes a status always runs under a user identity and is written to the audit trail. Whether an email is sent is a choice made by that same person.
