Frequently asked questions

Request founding access from the website. After approval, use the invitation instructions to create your account. If you already have an account, sign in instead of creating another workspace.

Check the code against your invitation and use the email you were invited with. If it still fails, contact support with your agency name and the error message. Never send your password.

Have your agency and recruiter names, applicant-facing phone, monitored email, business mailing address, and public interview booking link ready. Then open the setup wizard. Your agency facts, hiring states, and a reviewed role come next.

No. You can set up your agency, publish roles, review applicants, and use your own interview booking page without GHL. Connect it later if you want applicants and permitted activity to reach your CRM.

The nine setup tutorials show the current screens, with narration and captions. Keep the getting-started guide open alongside them and begin with one role and a few cities.

No. A role in the Role Gallery is a draft you can review and reuse. Select reviewed roles, choose your states and markets, inspect the proposal, and confirm publishing. A city posting is the published version of that role for a particular market.

Read the title and description. Check the location, remote-work details, licensing requirements, employment type, and compensation disclosures. For commission-only independent contractor opportunities, say that clearly. Edit anything that does not accurately describe your agency.

The first press arms the publish control so you can check the selected rows. The second confirms it. Cancel if a role or market is wrong. Publishing runs in the background; wait for the batch and check Posts before assuming every row is live.

Save your default deployment states in Markets & launch or Settings → Brand Profile. These defaults restrict the supported city deployment and rotation flows. An empty selection allows every state with target markets, so review the selection before publishing.

Open Posts and check the actual status, locations, and expiry dates. In Verify launch, open your careers page and a role. Check the application and booking links before sharing. If a posting is missing or still processing, inspect its status and any explanation before retrying.

No. Your careers page, a distribution feed, and a listing on an external board are different things. Check Where your jobs appear for the channel’s current state. A feed being available does not prove a board has indexed it, and publishing does not promise applicants.

Postings have expiry dates. Rotation can prepare replacement postings when enabled, subject to your agency’s access, limits, and content checks. Review Posts and Rotation for the current state; an enabled setting alone is not proof that every replacement succeeded.

Find your careers link in Verify launch or Where your jobs appear. Share that agency-specific link, rather than a feed URL. The workspace shows your current posting capacity. Access and pricing can change after the founding period; contact support to confirm what applies to your agency.

Warp provides a shared sending domain. Save a monitored reply email and check the sender preview in Settings → Email. You can connect a supported mailbox or configure your own sending domain later. Send a test and read the received message before relying on it.

Recruiting outreach includes a postal mailing address in the email footer. Save a valid business mailing address in Settings → Email; it is separate from the email address that receives replies.

Connecting a mailbox makes it available; it does not choose it for the agency. In Settings → Email, select the mailbox under the sending choice and press Save choice. Confirm the preview and send a test.

Agency mail can be sent through the selected mailbox even while its owner is signed out. Review the connection permissions and make sure that account is appropriate for agency-wide use. Keep its authorization current.

Check the saved recipient and reply email, sender choice, and any connection error. Check spam or junk and inspect the actual received sender when a test arrives. If it is still missing, report the approximate send time and recipient to support; avoid repeatedly sending the same message.

Authorization and confirmation are separate. Open Settings → GHL Integration, test the connection, read the sub-account name, and confirm it only if it is your agency’s account. Then review pipeline and stage mapping. An unfamiliar name is a reason to stop and check the authorization.

Use the reconnect option in Settings → GHL Integration. If you use the manual option, enter a Private Integration Token from your own GHL sub-account and save it. Test the connection and verify the account name again. Keep the token private; do not paste it into a support report.

No. Inbound applicants can sync after the correct sub-account is confirmed. Sourced people do not automatically sync. An explicit, individual Push to GHL action is a separate choice. Review the person and destination before using it.

Open People and choose Applicants. Open the person’s details to review their application and activity. Talent pool and Applicants are different views; someone you sourced is not automatically an applicant.

Use a public Calendly, GHL, or other scheduling page in Settings → Email. Check that it opens the correct agency’s interview calendar. Test the application and booking path yourself before sharing your careers page.

No. A sent invitation, scheduling link, or Interviewing pipeline stage does not confirm a time. Once your calendar confirms the appointment, open the person in People and record the confirmed interview. Reports shows upcoming recorded appointments separately.

Confirmed interview tracking is currently manual. Record the appointment after calendar confirmation, including its time and time zone. Make calendar changes in your scheduler, then reschedule or cancel the record in Warp. You can record additional interview rounds for the same person.

Open the Support tab in your workspace and choose Report a problem. Include the page where it happened. Describe what you expected and what actually happened, and attach a screenshot if useful. The report includes browser details. You can also email admin@warprecruit.com.

Include your agency name, the page or task, the error message, and the approximate time it happened. For email issues, include the recipient and send time. Crop or redact unrelated applicant information in screenshots. Never send passwords, API keys, or Private Integration Tokens.

Agency records are scoped to your workspace. A connected external account is a separate destination, so always verify the GHL sub-account name and selected mailbox. If something appears to belong to another agency, stop that action and report it to support.