Payment onboarding
Include your business name, provider, application stage, and the help you need. Do not email card numbers, security codes, bank credentials, or processor passwords.
GivePay support
Support
Tell us what is blocked and where the workflow should go next.
GivePay supports payment onboarding, AI agent setup, checkout and billing questions, integrations, and custom implementation. Send enough context to identify the workflow, but never send payment-card security data or passwords.
AI agent configuration
Include the agent or template name, your website, the affected channel, and a short example of the expected behavior. Remove unnecessary personal or sensitive information.
HighLevel connection
Include the GivePay intake ID, whether you installed at the agency or sub-account level, and the connection status shown after authorization. Never send access tokens, refresh tokens, client secrets, or HighLevel passwords.
Billing and orders
Include the GivePay order or receipt identifier and the email used at checkout. Provider processing and usage charges may need to be handled directly with that provider.
Security concerns
If you believe an account or integration is compromised, disconnect affected access where possible and contact GivePay and the relevant platform or payment provider immediately.
New implementation
Launch a new AI or payments workflow.
Use the guided launch intake when the request needs business goals, files, integrations, approval rules, or a human-handoff plan.