Customer Can’t Open Your Quote PDF? Check Drive Access Before Resending

You sent a Google Drive link to a quote PDF, but the customer says they cannot open it. Start with the exact link and intended reader—not another copy of the file or a wider sharing setting.

A quote can contain customer-specific prices, addresses or project details. An access problem is not a reason to make it available to everyone with the link. Find the failed step, have the authorized owner make the smallest approved correction, and check the recipient’s result.

Confirm which quote link was sent

Open the link from the actual sent message in your own approved account. Compare the document with the quote your team intended to deliver: customer, revision, date and scope. Keep the original message as evidence; do not replace it with a screenshot of a different file.

If your team cannot locate the intended file, resolve that first. Permissions on the wrong PDF do not fix delivery. If you can open it, that proves your account has access—not that the customer does.

Ask what the customer sees: an access request, an unavailable file, a preview that will not load, or a missing download option. Record the message without asking them for a password or collecting unrelated account details. Opening, previewing and downloading are separate checks; avoid calling all three “the link is broken.”

Match the recipient account to the sharing entry

In the file’s sharing dialog, inspect the exact recipient entry and current role. Compare it with the address your business approved for that quote. Do not grant access to an unfamiliar address merely because someone requests it.

Google’s Drive sharing instructions explain sharing with specific people and choosing a role. For files in My Drive, Viewer permits viewing but not editing; download availability can be controlled by the owner. Treat a download restriction separately from permission to read the quote.

When multiple accounts are involved, ask the recipient to check which account they are using. Google’s access troubleshooting guidance for its document products specifically calls out the account a file was shared with and possible work-account policy restrictions. That guidance is not proof of the cause of this particular PDF failure; use the actual file and account evidence.

An illustrative comparison might read: “Approved reader: customer’s business address. Sharing entry: that same address. Reported account: customer’s personal address.” The mismatch is a lead to investigate, not permission to add the personal address automatically. Confirm the intended recipient before changing anything.

Keep the correction limited to the approved reader

Have the file owner or authorized operator inspect general access as well as the named recipient. Google distinguishes restricted access from access for anyone with the link. Choose a correction that fits the approved audience; do not use broader access as a troubleshooting shortcut.

If access comes from a parent folder, inspect that relationship before changing the file or folder. Google’s sharing guidance notes that folder access is inherited. A folder-level change can affect more than this quote. Escalate a policy restriction to the responsible administrator instead of copying the file into another account to evade it.

Keep permissions and delivery separate. If the sharing correction may notify the recipient, account for that in your communication plan. Do not send several new links while one access request is unresolved. A short explanation of which link to use is more useful than leaving the customer to choose among old and new versions.

For example, a proposed reply could say: “Please use the quote link in our message dated [date]. It is the [revision] version. We have checked access for [approved address]. Let us know whether it opens and shows the expected project.” Send that only after the described checks actually happened; brackets are placeholders, not facts.

Check the recipient-side result before closing the issue

Ask the intended recipient to open the exact link using the approved route and confirm the expected quote version. If download is part of your delivery promise, check that separately. Do not ask them to forward the private quote to an unapproved test address.

Use a synthetic file and business-controlled test account when you need to investigate your workflow without exposing a real customer quote. A test proves only that sample route. It does not establish that a customer read, understood or accepted the offer.

Record the outcome precisely: correct file opens, download works if required, or an exact unresolved message remains. Access granted is not quote approval. A sent email is not recipient-side proof. If the issue persists, give the owner the file reference, recipient identity, error and checks already completed so the next investigation starts with evidence.

AI can draft the checklist from fictional details without receiving the quote:

Create a file-delivery troubleshooting checklist for a fictional customer quote. Separate file version, approved recipient, sharing role, preview and download. Do not grant access, send messages or claim the customer opened the file.

Review that checklist against the actual sharing interface. For the broader next-action process, use the small-business CRM handoff guide. If your team needs help mapping quote creation, delivery and follow-up as separate checkpoints, contact Business Boomer about a scoped automation review.