Skip to main content
No. Describe the page or form to your connected AI. You can also use the visual form builder and dashboard.
No. You only need to copy https://jobing.site/mcp into a compatible AI app and approve access.
Jobing works with AI apps that support remote MCP connectors and browser sign-in. The docs include current steps for ChatGPT and Claude.
No. It gives your existing AI app approved tools.
Yes. Use the dashboard for pages, forms, responses, sharing, integrations, and billing.
No. A new form is a private draft. It becomes public after you publish it.
Yes. Edits are saved as a new draft. The current live version keeps working until you publish the changes. Existing responses remain attached.
Yes. Use native HTML and style every visible part. Keep the Jobing action address and question names. You do not need an iframe.
Yes. Every published form has a hosted form link.
They arrive in the private response inbox for that form.
No. It needs separate response permission and reads visible responses when you ask it to.
No. It receives basic file details, not the contents. The signed-in owner can download the file.
Valid submissions continue being accepted and saved. Responses beyond the monthly viewing allowance stay locked until you upgrade or they become available under your allowance.
No. The monthly plan limit controls owner visibility, not visitor submission.
Jobing blocks another form creation or publish action. Existing live forms continue working.
Yes. Connect the Email integration to send readable new-response summaries to up to 10 team addresses. Automatic visitor confirmation email is not currently a connector feature.
Not currently. It can collect a preferred date and time as a request, but it does not check live availability.
Not currently. Do not collect payment card details in a Jobing form.
No. Pages is for focused browser-based pages. Private server logic, custom databases, accounts, and full applications need other tools.
Yes. Open Connected AI apps and remove the connection.
No. Updating a page keeps its public address.
Yes, on Starter and Business plans. Connect a root domain or subdomain, add the DNS records shown by Jobing, then assign each page a path. A dedicated subdomain such as pages.example.com is safest when your main website already exists.
Yes. Pointing example.com to Jobing sends that domain’s website traffic to Jobing. Use a subdomain such as pages.example.com unless you intend to replace the root website.
No. The original jobing.online address remains available as a fallback.
Yes. Give each page a unique one-part path such as /contact, /jobs, or /summer-offer.
No. The old custom path stops working. Update advertisements, QR codes, emails, and other external links before changing it.
No. Page deletion is permanent and requires explicit confirmation.
Yes. Export responses visible on your current plan as a CSV file.
Still unsure? Open Troubleshooting or send feedback.