Reading a Query Execution Plan

Understand why a query with a filter on an unindexed column triggers a full table scan.

A query 'SELECT * FROM orders WHERE customer_email = ?' shows a full table (sequential) scan in its execution plan, even though the table has millions of rows. Which change is most likely to eliminate the full scan and improve performance?