> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/general/how-to/how-to-create-bios-for-your-team.md). # How to create bios for your team Having a bio on your website can be an invaluable tool for establishing trust and credibility with potential visitors. It's a great way to give customers an insight into who you are and why they should choose your services. Not only can bios help you build relationships with customers, but they can also boost your visibility and authority on the web. **Once you have some or all of the information below, send it over to and we'll do the rest!** **PHOTO (HEADSHOT)** Need tips? {% content-ref url="/pages/Li1vDieXYUqf3phamwl9" %} [Tips for an upcoming photoshoot](/docs/branding-and-onboarding/tips-for-an-upcoming-photoshoot.md) {% endcontent-ref %} **MEET THE PROVIDER** * What does the provider want to be known for? Experience? Compassion? * How long has the provider been in practice? * Special interests (as opposed to specialties) This would be, for example, helping people feel better about themselves, focusing on the underserved, building trust with patients, etc.) * Is the provider involved in any philanthropic work, volunteering activities, community involvement, etc.? **SKILLS AND SPECIALTIES** This part of the bio always incorporates the top procedures provided by the provider **EDUCATION AND TRAINING** It’s very important to have the doctor’s education and training history available on the website. Where they obtained their degrees, residencies, fellowships, additional training, etc (schools and city/St.). Dates aren’t required, but they are helpful if available **PROFESSIONAL MEMBERSHIPS/ASSOCIATIONS** A good bio talks about the societies and memberships as well as current organizations and associations the physician is involved with. **LEADERSHIP AND APPEARANCES** (optional) Speaking engagements, ongoing media appearances, lectures or training for other surgeons, research and development **AWARDS AND RECOGNITION** (optional) Special recognitions, awards, mentions in magazines, publicity, etc. **PERSONAL** (optional) This can be short and sweet. Married, how long, wife’s/partner’s name, how many children, hobbies, things enjoyed in spare time, etc. ### **STAFF BIO INFO:** * Name * Professional title * How long in practice / how long with current practice * Main daily duties * Something personal (favorite part of working with the practice, what led to the career choice, family if applicable - partner, kids, hobbies, etc.) * Photo (Headshot) {% file src="/files/laPk94CBELvhtyBuqZwH" %} {% file src="/files/9oGEVZtEbqG7wNtY6Ofq" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.doctorlogic.com/docs/general/how-to/how-to-create-bios-for-your-team.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.