Agiled Docs
Troubleshooting

Public Link Issues

Fix public forms, booking pages, invoices, estimates, checkout, and document links.

Public links let customers submit forms, book appointments, view invoices and estimates, pay checkout links, and sign documents.

Start by testing the exact link the customer received in a private browser window. Public links should work without an Agiled session unless the page is intentionally private.

Confirm the copied link is the latest public link. If the workspace uses a custom domain, confirm DNS is verified and the custom domain is active.

Also check whether the link came from an old email, copied browser tab, draft record, previous estimate revision, inactive booking page, or archived form. When in doubt, copy the link again from the current record inside Agiled and test that version.

Ask the customer to confirm the full URL they opened when possible. A screenshot of only the page is often less useful than the exact link, because old links, custom domains, and copied draft URLs can look similar.

Custom Domain Problems

If the workspace uses a custom domain, confirm:

  • DNS records match the values shown in Agiled.
  • The domain is verified and active.
  • The public page works on the default Agiled link.
  • Browser cache or old DNS results are not hiding a recent change.

DNS updates can take time. Use the default public link for urgent customer actions while the custom domain finishes propagating.

Check that the form is published and required fields are valid. Submit a test response before sharing the link again.

If the form is embedded on a website, test both the direct public form link and the embedded version. If the direct link works but the embed fails, review the website embed code, page cache, and whether the website is blocking scripts.

Check event type availability, user availability, buffers, connected calendars, time zone, and existing appointments.

Open the booking page as a customer and test a date range that should have availability. If no slots appear, compare the event type schedule, assigned user availability, connected calendar conflicts, booking lead time, and timezone display.

Check that the record is active, the payment gateway is connected when payment is expected, the customer has the correct link, and the status still allows the action.

For documents and estimates that require signatures, verify the recipient still has a pending signing action and is using the newest signing link. If the recipient already signed, the public page may no longer show the same action.

If payment fails on a checkout or invoice page, test whether the page loads before changing gateway settings. A link problem, gateway problem, and card decline are different issues with different fixes.

Before Contacting Support

Collect:

  • The exact public link.
  • The workspace domain or custom domain used.
  • The record type and record name or number.
  • The customer action that failed.
  • A screenshot of the error or empty state.
  • Whether the same link works in a private browser window.

Also include the browser, device type, and whether the issue happens on the default Agiled domain, the custom domain, or both.

Fast Isolation Steps

  1. Test the exact customer link in a private browser window.
  2. Copy a fresh link from the current Agiled record.
  3. Test the default Agiled domain if a custom domain is used.
  4. Check the source record status and public sharing settings.
  5. Test the customer action with a low-risk record when possible.

On this page