NewResilience, Continuity, the Pro levels and Agentic Verification: from safekeeping to proof you can recover.The new line-up is here.See what's new
A page for customers, so the hero leads with their two most common actions. Production's /contact-support is "Help for existing Codekeeper customers": live chat first, then email. Visitors here already have an account, so the hero buttons are Log in and Email support, not Book a demo. This is a deliberate exception to the hero rule for a support page (the offer band is optional here too). Book a demo stays in the navigation, in a text link for prospects who land here by mistake, and in the final CTA.
  • The login link is production's: https://app.codekeeper.co/login.
  • Support email: production uses service@codekeeper.co on this page and on /cancel. The kit's FAQ page uses support@codekeeper.co and contact@codekeeper.co instead. Confirm one support address and use it everywhere.
  • The ticks: "dedicated contacts" comes from the FAQ (production Q34, onboarding). ISO/IEC 27001:2022 is confirmed.
Support

Already a customer? We're here to help.

Chat with the support team, email us, or log in to manage your applications, deposits and agreements.

Not a customer yet? Book a demo or contact sales.

  • Support from experienced specialists
  • Dedicated contacts for legal, technical, compliance and billing
  • ISO/IEC 27001:2022 certified
Every support route, in order of speed. Production lists two routes on this page: live chat ("the quickest way to get help") and email. The three briefing calls are production pages too (/book-support-briefing-call, /book-technical-briefing-call, /book-legal-briefing-call), each with a HubSpot scheduler; they're the right place for setup, deposit and agreement questions, so they're surfaced here instead of being buried under Resources. The card copy is each call page's own description, shortened.
  • Chat: in production, the button opens the HubSpot chat widget. In this kit it does nothing.
  • Release requests go to contact@codekeeper.co, as production's "Have a quick question?" block says. The process line is from the Trust Center FAQ; operations should confirm it.

Get help

Pick the fastest route for your question.

Live chat is the quickest way to get help. For anything that needs a closer look, book time with a specialist.

Chat with support

The quickest way to get help. The chat sits in the corner of every page.

Email support

Send us an email, with your account name, and we'll get back to you.

service@codekeeper.co

Log in

Your applications, deposits, agreements and team, in one place.

Log in

Account support call

Guided help with account setup, procurement onboarding or compliance documentation, such as due diligence questionnaires.

Book an account call

Technical briefing call

Connecting repositories, preparing your deposits, and choosing manual upload or automated sync.

Book a technical call

Legal briefing call

Reviewing or redlining an agreement, clarifying release terms, and getting ready to sign.

Book a legal call
Requesting a release? Email contact@codekeeper.co. We validate every request before any materials become accessible: a legal review, verification of the release condition and authentication of the beneficiary.
The answers customers look for most, one click away. Billing, cancellation and "what does the new line-up mean for my plan?" are the questions the launch will raise, so they come first. The existing-customer line reflects the internal decision (plans stay as they are until renewal) and is the same wording as the FAQ; customer success must confirm it before launch.
The people behind the support inbox. Production shows Lindsey and Robyn with photos, then "Or any other Customer Success Consultant". Lindsey is also named in a customer review ("Lindsey and the Support Team at CodeKeeper are on point"), which makes the card credible. Two production lines are reworded: Lindsey's "you'll never feel like you're in this alone" (an absolute) and the em-dash in Robyn's. Confirm before launch: both names, roles and photos are current, and both are happy to be shown. The photos load from codekeeper.co; where they can't load, the name shows instead. The kit has no person-card component, so each photo uses a small inline style for its round crop.

Talk to real people

Support from experienced specialists.

Every support request is handled by people with hands-on experience in software, compliance and resilience.

Lindsey, Customer Support at Codekeeper

Customer Support

Lindsey

Problems handled, software protected, and someone with you at every step.

Robyn, Customer Support at Codekeeper

Customer Support

Robyn

Part legal, part customer success, and fully focused on helping you protect your software.

Customer Success

Or any other consultant

We've all helped secure systems like yours, and every request is picked up by someone who knows the platform.

Guidance for the colleagues who get pulled in. Production's "Helpful guidance for different roles involved in software escrow" lists six briefings. They're kept as one row of links, with production's role names, so a customer can forward the right one to legal, procurement or IT without reading all six.

Briefings by role

Bringing in a colleague?

Each briefing explains what that role needs to do, and when, so setup doesn't wait on a meeting.

The same close on every page. Existing customers are the warmest audience for the new line-up, so the support page closes on what's new instead of a generic close. Every page ends on the same two actions in the same order: Book a demo, then the sample evidence pack.

Want more from Codekeeper? See what's new.

Resilience, Continuity, the Pro levels and Agentic Verification are here. Ask your account manager, or book a demo to see them on your applications.

Chat widget goes here. Production runs HubSpot chat in this corner. Keep it on launch: it catches visitors with a quick question who won't book a demo yet. Route it to sales during office hours.