Start with what you see on screen. Pick the closest match below and follow it. They are ordered by how often each one turns out to be the answer.
Echo shows the same message, Please complete the required fields, no matter why a sign-in failed. A wrong password, a mistyped email address, the wrong ministry's web address and a removed account all look exactly the same. The message is not a hint, so do not read anything into it.
The page says "Please complete the required fields"
Most often this means you are at the wrong web address. Every ministry has its own Echo address, and your account exists on one ministry only. Echo works out which ministry you belong to from the address in your browser, and sign-in pages look identical at every address.
Check: are you at the address from your invitation email?
If yes → go to the next symptom, Echo does not accept my email address.
If no →
Open your invitation email and use the link in it. That is the safest address to use.
Sign in again with your email address and password.
If you serve with more than one ministry, you have a separate account at each address, each with its own password. The same email address on two ministries is two different accounts.
If the address is wrong altogether, you get a "page not found" error rather than a sign-in form. That is a clue, not a fault.
Echo does not accept my email address
The first field is labeled Username or email, but Echo only signs you in by email address. It has to be the address your account was created with.

Check: is what you typed an email address, and is it the one your account was created with?
If yes → go to Echo does not accept my password. Capitalization does not matter here, so Maria@example.org and maria@example.org reach the same account.
If no →
Find the invitation email Echo sent you. Whichever inbox it arrived in holds the address on your account.
Type that exact address into the field. A username, a nickname, an alias, or the same name at a different domain will not work.
If you have both a personal and a ministry address, use only the one your account is on. The other will never work.
Cannot find the invitation? Ask your ministry supervisor which address is on your account.
Echo does not accept my password
Passwords in Echo are case-sensitive, and the field hides what you type, so a typo is invisible. Grace2026 and grace2026 are two different passwords.
Check: type the password by hand. Is Caps Lock off, and is there no space before or after it?
If yes → go to It fails the same way every time.
If no →
Turn Caps Lock off. On a phone, check that the keyboard has not capitalized the first letter for you.
Remove any space at the start or the end. If you copied the password out of an email or a message, a trailing space usually comes with it, and it counts as a character.
Type the password again and sign in.
If you are not sure what you are actually entering, type the password into a note on your phone or computer first, where you can read it back letter by letter. Then type it into Echo and delete the note. Echo passwords are at least eight characters long, so anything shorter is not your Echo password.
It fails the same way every time, even with the right details
If a wrong email address or password was saved in your browser at some point, the browser refills it every time the sign-in page loads. Every attempt then fails the same way, because the same wrong details are sent each time. It looks like Echo is refusing a correct password. It is never seeing the correct password.
Check: open a private or incognito window, go to your ministry's Echo address, and type your email address and password by hand. A private window ignores everything the browser has saved. Does that sign you in?
If yes → the saved details are the problem. Clear them:
Go back to your normal window and open the sign-in page.
Click into the email field and delete everything in it, including anything the browser filled in for you.
If a saved suggestion drops down under the field, remove it there. In Chrome and Edge, highlight the suggestion with the arrow keys and press
ShiftandDeletetogether.Do the same in the password field.
Type both by hand and sign in. When the browser offers to save them, let it. This time it is saving the right ones.
If the browser keeps filling them back in
The entry is stored in the browser's own password manager and has to be deleted there. Open your browser's settings and find its saved passwords, then delete every entry for your Echo address.
Chrome and Edge: the password manager in the browser's settings menu.
Safari: Settings, then Passwords.
Firefox: Settings, then Privacy and Security, then Saved Logins.
If you use a separate password manager such as 1Password, Bitwarden or your phone's built-in one, check there too. It may be the one doing the filling.
If no → go to I forgot my password, or the reset email never came.
I forgot my password, or the reset email never came
If nothing above gets you in, reset the password. The reset looks for your account on whichever ministry's address you are at, so the address has to be the right one here too.
Check: did you use Forgot Password? on the sign-in page, and did an email from Echo arrive?
If yes →
Open the email from Echo and follow the link. It works once, so request another reset if you need a second link.
Set a new password of at least eight characters.
Echo returns you to the sign-in page. Sign in with the new password.
If no →
Go to your ministry's Echo address and click Forgot Password?
Enter the email address on your account and submit it.
Check your spam or junk folder if the email has not arrived within a few minutes.

Echo tells you that instructions have been sent whether or not it found an account for that address. So the confirmation on screen is not proof that you typed the right address. If no email arrives, that is the real signal: either the address is not the one on your account, or you are at the wrong ministry's web address.
You can request at most three resets for the same email address in twelve hours. After that Echo stops sending them and tells you the limit has been reached. Wait, or ask your ministry supervisor to set a password for you.
Echo asks me for a code
If your password is accepted and Echo then asks for a code, nothing has gone wrong. That is two-factor authentication, and your ministry may have turned it on for everyone.

Check: look in the inbox for the address on your account. Echo emails the code there.
If yes → type the code into Echo.
If no → check your spam folder. Then see 2-Factor Authentication for how it works and how to use an authenticator app instead.
"This tenant is no longer active" or a maintenance page
Neither message is a failed sign-in, and neither is anything you can fix from the sign-in page.
Check: which one do you see?
"This tenant is no longer active." Your ministry's Echo account is not currently active, so nobody there can sign in. Reach out to your ministry supervisor if you believe this is a mistake.
A maintenance page. Echo is being worked on. Try again shortly. Nothing is wrong with your account.
Still stuck
If you have worked through everything above and it still will not let you in, the account itself may be the reason. Echo shows the same message for a removed account as it does for a mistyped password, so you cannot tell the difference from the sign-in page.
Ask the Echo administrator (Ministry Supervisor) at your ministry to confirm three things:
The account still exists and has not been removed.
The exact email address on it.
The web address for your ministry.
They can also set a new password for you, which sidesteps the reset email entirely.
If you write to support, include the web address you were at, the exact words of the message on screen, the time you tried, and which checks above you already ran. That lets the first reply be the fix.
Repeated failed attempts do not lock your Echo account. If you have tried ten times, the eleventh is no more likely to be refused than the first, but it is no more likely to succeed either, so stop and work through the checks above instead.