Skip to main content

Getting In:
A College Coach Conversation

Tune in for expert insights from the Bright Horizons College Coach® podcast, Getting In: A College Coach Conversation.

Tune In college podcast hero image
Elizabeth Heaton Podcast

Getting In: A College Coach Conversation

A Member of the NACAC Podcast Network

Tune in for expert insights from the Bright Horizons College Coach podcast, Getting In: A College Coach Conversation.

Every week, hosts Ian Fisher, Sally Ganga, Shannon Vasconcelos and Kyra Tyler gather former admissions and financial aid officers as well as outside guests for candid, behind-the-scenes talk.

A sampling of subjects:

  • Questions you should never ask an admissions officer
  • Can you appeal financial aid decisions?
  • Tips for acing your interview
  • Myths about admissions decisions
  • Is it better to get an A in college prep or a B in honors?
  • Negotiating additional merit aid
  • ...and more!
New episodes come out every Thursday. Visit this page if you have questions you’d like to submit for an answer on air.
Listen To: July 02, 2026

Listen To: June 25, 2026

Listen To: June 18, 2026

Listen To: June 11, 2026

Listen To: June 04, 2026

Interested?

Interested in learning more about how our college admissions counseling services can help your student succeed?

Call 877-402-6224 or complete the form for information on getting your student started with one of our experts.

Inclusion Matters Here Pride Flag

For information on the services available through your employer-sponsored College Coach benefit, contact helpdesk@getintocollege.com.

 


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>