Knowledge · Business Operations

    Attachments and Communication History

    Photos, documents and message history are evidence. How to keep attachments findable, tied to the right record, and available after the people involved have left.

    Where should photos and documents sent to customers be stored?

    On the record they concern — the job, estimate or invoice — with the conversation linking to them rather than owning them. Attachments living only inside a message thread or a personal phone are effectively lost the moment someone needs them for a dispute or a warranty claim.

    Key takeaways

    • An attachment inside a thread should also be attached to the record.
    • Attachment delivery is channel-dependent and never guaranteed.
    • History is only useful if it is searchable by person, record and date.
    • Photos are the most valuable evidence a service business generates.
    • History must outlive the employee who created it.

    What history has to answer

    • What did we tell this customer, and when?
    • What did they agree to, in writing?
    • What did the site look like before we started?
    • Which version of the document did they actually receive?
    • Who sent it, and are they still here?

    Why attachment delivery is not guaranteed

    Sending a photo by text depends on carrier support and size limits. Email attachments can be stripped by a filter or bounce for exceeding a mailbox limit. A link to a portal avoids most of that, but requires the customer to log in.

    Because none of the paths is certain, the practical rule is: store first, send second. If the file lives on the record, a failed send costs a resend, not the evidence.

    Making history survive people

    The most common evidence loss in service businesses is not a system failure — it is a technician with two hundred job photos on a personal phone leaving the company. If the photo was never uploaded, it never existed as far as the business is concerned.

    The fix is habit plus a place: capture into the job, not the camera roll, and make finding a past job faster than scrolling a phone.

    Where URBLD fits

    URBLD stores message attachments with the thread and lets individual messages be attached to a job, so photos and documents shared in conversation can be pulled onto the record they concern. Inbox threads can also be summarised by AI. Whether a carrier or mailbox provider delivers a given attachment is outside any platform's control.

    Principles reinforced

    This page rests on the following foundational ideas.

    FAQ

    Frequently Asked Questions

    Straight answers about how URBLD runs the business end-to-end.

    More in Business Operations

    The daily mechanics: workflows, checklists, scheduling and handoffs.

    Browse Business Operations
    Share this page